Hi Wayne,
The link below by power-broker contained a possible solution (putting a SET FOXPROW = -saveregs into the autoexec.bat file [or now it goes in autoexec.nt as far as I know] but great sadness, I tried it and it locked me out of FPW. And even worse, even after removing the autoexec entry, I cannot get back into Foxpro anyhow - the program starts to fire and I get the splash screen but as soon as I do, it quits (and nothing shows in the Task Manager so I am pretty sure it is not running).
I tried the following:
1) reboot
2) looked to set if the DOS var was in the DOS environment
3) tried a bunch of the "compatibility" settings available from the shortcut for "DOS" programs
4) tried deleting the Foxuser.* files
5 renamed Config.fpw so that I loaded somewhat cleanly
Have run out of ideas....the only thing that has changed on my computer in the last few weeks was a monitor. I changed from a CRT to an LCD and went from 1024 x 768 (honkin big 19" Sony) to 1280 x 1024 (19" lcd). I tried setting back the resolution. I only did this because a user a few years back had trouble with running the program and I asked him what had changed and he had put in a new fast gaming video card. Once he switched back to some slower mode, the problem disappeared. I don't know if my issue is the video change or not - could just be a rabbit trail.
Oh, I wish I would have "ghosted" my whole hard drive a few days ago - just bought an external hard drive to start doing so but not yet set up!
Thanks for any help....
Albert
>I did a google search, and found these;
>
http://www.power-broker.com/internalinconsistency.htm>
>
http://www.foxite.com/archives/0000013519.htm>
>
http://users.aol.com/FoxProResources/Q111264.txt>
>
>
>>Hi,
>>
>>I have an app written in FPW2.6 that of course, is not going to be replaced anytime soon but I have to maintain it. I get the error "Use of transgressed handle" when firing one of the screens (.spr). I searched MSFT and did not come up with anything. Same thing with Google. It only happens on one screen but it happens "near" the same line each time I fire that screen.
>>
>>Albert
