>>>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!


a. 0 problem is well documented (so well that i can't remember the exact cause, i think something in format or picture stays when entering unless whole field is selected)

b. at least they didn't write this in visual basic...