>But Im just curious to know.... was it the failure of
>apps to NULL out objects after using them that cause all
>those VFP 6 C5 errors?

It seems easiest to quote a post (msg #17867)

Rich Addison wrote:

>Many people keep referring to "the" C000...5 error.
>
>I had the impression that a C000...5 error was to VFP like a GPF was to Win3x ... sort of a catch-all "something's really hosed here" message.
>
>Am I mistaken about that? How specific is the meaning of a C000...5 error?
>

Ed Rauh replied:

There is a specific meaning to it from an operating system perspective, but an awful lot of things can cause it to happen. in essense, it indicates that your application tried to access a memory location that didn't belong to it (or may not even exist!) There are specific conditions that are known to cause the error to appear (the closedown C0000005 where DCOM is not present is one; sending a bad value to the RGB() function at times, etc.) and in these situations, where you can point to a specific, recreatable error, there are often workarounds. But, yes, the error is generic and there is no single cure for all occurances of it.