>>>>Am I the only one out here who sees VFP 5.0a crash and burn on a regular basis? <<
>>>
>>>Say, I'm "fed" up here too...Recently I had a whole slew of crashes in 5.0a, for a couple days. I finally found it was the fact that I had switched page names and page order on a very busy pageframe too many times. I redid the pageframe, and no more crashes. You might look for something specific like that...does it always occur in the same project, same form involved, for instance? <
>>
>>Hi Bruce, it looks like I'm working just down the street from you (at FERC, do you know a guy named Evan?). Anyway, I've been seeing all kinds of weirdness: One day VFP crashed during a debug session and I was presented with a debug of VFP's internal C code! Another time (twice, actually) VFP took all the files located in my Data directory and dumped them into the root of the project, the program flipped out because it couldn't find the data files. I start looking for them and found them in the project root directory. What kind of nonsense is this? Just this morning, I'm keying some numbers into a table and (almost) every timeVFP added a 0 to the end of the integer portion of the number, so $700 becomes $7000 and 123.45 becomes 1230.45 This is total bullshit and causes me to question my own integrity when I stand in front of a client and recommend using VFP for their important development projects. It seems to me MS spends far too much effort adding bells and whistles and
>>almost none to fix a buggy product. I bet a nickel we'll not see a fix between now and the release of 6.0, no time for it, gotta push the new product - jerks!
>
>Richard,
>
>There are alot of developers that are NOT having the problems you are having. I have been using Fox products sionce the early 80's and I have never seen Fox move data files on its own. Most of the replies you are getting are suggesting that perhaps there is a remote possibility that your code might be at fault here somehow.

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