>Robert,
>
>When the error occurs in the method code of an object, it's error method fires off, so the object still has "code on the call stack". An object can't be released if it has code executing because that would invalidate the call stack and crash most miserably.
<<...Snip>>
Hi David,
I have written a DLL that allows me to cause a ProgrammaticChange event to fire when VFP returns to a wait state. Wouldn't this allow the error routine to create an error object, push it onto an error stack, and have the ProgrammaticChange code process it after control has returned from the error method? It would seem that cleanup would become much easier. Please let me know what you think of the idea.
Thanks,
Ned