>I am trying, unsuccessfully, to debug a C0000005 error in some legacy code (VFP6, sp4). This is a very large app, developed in late 1990's and originally based on CodeBook framework. I added a new class to it and believe I have released all objects that I have created. Leaving out a lot of compliations, it basically runs Main.prg which runs Setup.prg which runs RunClass.prg which instantiates and runs my new class. When run in production mode, it completes the functionality of my class, returns to to Runclass (which releases all objects it runs by just letting them fall out of focus), returns to Setup which then aborts with a C0000005 on a Clear Memory statement. When it aborts the only thing in the call stack is Setup.prg and Main.prg. Disp Memory shows no extraneous variables hanging around. When I run in debug mode, it generally does not C5.
>
>My question is, how can I detect what is causing the C5??
>How can I identify what non-visual objects may not have been released?
>The code outside of my class has been running successfully since May of 2000, which is why am reluctant to change the way Runclass.prg 'releases' objects. So I'm sure there is something new I introduced with my class, but since I released all the objects I created (by setting them to .null. in the destroy method of my class) I don't know what to look for.
>
>Can anyone help?

Could it be that you're releasing your objects in the wrong order (e.g. release parent before child)? For now try to comment out all the releasing code and see if there would be a difference.

Also could it be a corrupted classlibrary or some table?

Here is link to Doug's blog
http://doughennig.blogspot.com/2006/04/dont-return-inside-with.html