>Problem 4
>The thing that is really bugging me - unrelated to the above, is the frequency with which VFP5 is crashing.
>This invariably happens soon after I encounter a runtime error in my testing. I can generally cancel the program and close all files, but the next time I rebuild the app, VFP will likely cause an exception error and crash - Dr. Watson I presume!
>A couple of developers I've spoken to say this hardly ever happens to them. I see it several times a day.
>I've tried reinstalling, maximizing Windows Virtual memory size,etc.
>I'm using VFP 5 Prof. Ed. running on NT Workstation 4. Any ideas why this might be happening?
>
>I've scoured the documentation for answers to the above queries, to no avail. I've developed applications in several relational DBMS's in the past, but VFP is rapidly becoming the most frustrating!
>
>Any help much appreciated.
>
>Martin Thomson
>Systems Analyst, B.C. Govt

I too experienced many crashes when I first started using VFP. But it got better as I learned some of the things which will definately produce crashes. I even spoke to M$ about this because of my frustration level. What I was told was that VFP is "not very good" at handling certain errors. Most especially when you have a reference to an invalid object (one that doesn't exist). Mostly what caused my crashes was after the error message, trying to open the debugger. If I simply cancelled after this type of error instead of Suspend, things would work out a lot better for me. I was also told that one of the biggest problems is a conflict with video drivers. There was a thread here not long ago about video drivers which suggested changing to a "plain vanilla" driver and see if that helps. I haven't changed my driver yet (although I plan to because now my Help compiler is wigging out all the time), but something that did help a lot was to lower the performance setting in the Display properties on my machine.

Hang in there! Trust me, it gets better!