>>>>>Am I the only one out here who sees VFP 5.0a crash and burn on a regular basis? <<
>>>>

>Richard, I'd like to add my 2 cents worth of agreement with Jim. Twice I've had the kind of problems you're talking about, once with file trashing under Windows 3.11 and another time with the 'Illegal Operation' in Win95. The first was a hardware problem - bad memory chip, although it LOOKED like VFP because running VFP pushed the chip 'over the edge'. The second time was bad coding on my part. When I exited a program due to bugs and left object variables behind, I crashed. That's still a problem when working on new forms, but knowing the cause means the only time I waste is re-starting VFP.
>
>I still get the 'illegal operation' occasionally, but I know it's MY fault, not MS. They aren't perfect, not even close, but my blood pressure is a LOT happier since I stopped being angry at them and started accepting their foibles/bugs/'features'. If you think MS is bad, try Oracle!
>
>Barbara

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-