>>From what you say in a further message and from my hardware experience (extensive, about 800-1000 computers) I would say you have some bad memory on your computer. The bad thing is that in such kind of problems, no test program will help. I saw about 15-20 computers like that. I remember only one case when it was the motherboard. In all other cases, it was the memory.
>>
>>I assume the computer is correctly setup (the boot setup). For tests, try to set default settings.
>>
>
>Paul, thanks for the reply. I (and others) have seen this behavior on too many different computers for us to believe that we all have bad memory or motherboards or whatever. This is, plain and simple, a buggy piece of software that needs to be fixed by the jerks at MS. Just this morning I crashed during running because I refenenced a non-existent form object (I mis-spelled the name). I got the error and debug window and then the infamous "This program has performed an illegal operation, please contact the program's vendor if the problem persists..." I shut down VFP and re-started it, but found out it had trashed my project file!!! Thank God for SourceSafe.
>
>-RW-
My 2 cents worth... if your so dead set that its just plain and simply buggy software then why come here looking for help or answers? And there was a comment made somewhere in this Thread about video drivers...

I too have been dealing with Fox sidestepping quirks and whatnot since the 80's, and your situation sends up a red flag I learned long ago. Unrepeatable errors, Weirdness, Constant Crashes on simple tasks = Video Driver conflict.

Have you tried the using the standard windows video driver? I've seen vendor drivers work fine with FP/VFP on one machine and not another. And have you tried abusing the machine with other software packages like Paul suggested? Thats the first thing I do if I cant identify a problem. (Paul you just made my day with your MSWord tip... all this tme I thought i was nuts to think the same thing)

And lastly Richard if your problems are so Bizarre and unsolvable have you tried reporting them to M$?