I just did and got quite a few hits, would point you to just one of them, but there seems to be quite a few causes for this error, maybe best if you go look yourself.
This is not an error in your code. It is ultimately caused by a bug in VFP. There are many circumstances in which it manifests itself. The Microsoft Knowledge Base lists no fewer than 85 possible causes.
I suggest you follow Slighthaze's advice. If that doesn't get you anywhere, come back here and post more details of what you were doing when the error occurred.
Mike,
I agree with Andrea, many C0...05 errors are actually "holes" in the OS - that any application that fully exercises it will find.
I found a lot of "errors" in VFP 6.0 were fixed when I upgraded my Win98 system from 64MB to 96MB - it seems the Virtual Memory Manager in 98 didn't like "living on the edge" and VFP (along with the other things I had running) was keeping it just a little too busy!
In addition to the other suggestions, make sure you have installed all you VFP service packs. In particular, VFP6 SP3 specifically addressed the C0...05 error, I believe as it related to memory management.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.