Sometimes C5 is raised when a spawned object is active or focused and an event contained in the spawned object tries to release itself (suicide). A better way to release a spawned object is murder. Vacate the spawned object, return to the parent and then release [murder] it.

But VFP 8 and 9 have a lot of open issues. The error could be the result of faulty VFP error handling from some other issue in your app. If you read the XP SP2 fixes (I aint installing SP2 yet), there seems to be a mention that apps compiled on XP (SP1) might not work when installed on other OS versions.

If you can, write a seperate little app using minimal structures and try to recreate C5 (on a [very] small scale). Solve the problem on the model (if you can), and then report back what happened.

Point being - break in down to minimal components - use the noodle (or email Sergey:-) - and keep hitting the board till it gets fixed!

Does C5 happen with VFP 6? If you can, since VFP 6 is pretty stable, scale your app back and run under VFP 6. VFP six might give a more accurate picture of what is actually occuring than the C% VFP 8 throws at us (for almost any reason). Your not alone - late last night and early this morning I forwarded 5 or 6 VFP crash reports to MS - after that, I pressed the "do not send" button. I am reasonbly sure that only about 7 or 8 percent of the VFP crash reports are making to MS customer service because "we" developers don't want to stress MS's infrastructure:)


>Hi Friends,
>
>When I finish the executable the error message c0000005 is presented.
>
>Then I discovered that same inside of the development environment after I finish the program and the prompt returns for the command window, when I execute the command CLEAR ALL or QUIT the error message c0000005 happens also, in other words, the mistake happened in some point of the program, everything continued working usually until the moment of closing.
>
>The same problem happened in several different computers and with
>Windows 98, Windows ME and Windows XP
>
>The tests were accomplished with VFP8 SP1 and VFP9 Beta.
>
>Does anybody have some idea that can help myself to identify the mistake?
>
>Thanks in Advance,
>
>[]'s
>
>Dionísio