>Thanks for the reply, Barbara. I can see how exiting a running program with variables "floating" around in memory would cause you to get errors generated by VFP and I would expect this. What I do *not* expect, however, is for VFP to tell me I've performed an "illegal operation" when I'm trying to save a form, or edit a .PRG, or browse a table. I have seen ALL of these, on different machines, with different processors, and different OSs. Go figure. According to Jim, I'm a know-it-all malcontent whose code couldn't possibly be in error. He's right about one thing, my code is NOT in error. If it were my code, I could repeat the errors. I cannot. They seem as random as the wind. And I'm not the only one seeing this stuff, I work with 4 or 5 other developers who see weird stuff *all the time*. How do you work around saving a file???
>
>-RW-
Richard,

The single most common cause of Illegal opreation errors is a conflict with the video driver software being used on the machine. Illegal operation is comming from the OS and not VFP, it indicates that VFP has tried to reference a memory location that some other software has locked. Video drivers are famous for not respecting the memory space of other applications that are running. They do this to speed upo performance of the video by bypassing the the OS's memory allocation routines and grabbing their own memory.

Try using the Standard SuperVGS driver that shps with windows and see if it has any affect on you illegal operation errors.

I can only say that your experiences are not the same as mine and a whole lot of other people that I know who use VFP regularly and are not having the problems that you are.