Most likely you have a hanging reference somewhere that hasn't been released. Usually this is caused by a circular reference when an object is referenced by a parent and the child references the parent back. You should try to avoid this sort of stuff as much as possible or at the very least ensure that you clean up your references in the Destroy() method of the class. These things will leak memory over time if hte app runs for a while.

For quitting this isn't as much of a problem as you can release this stuff.

For just about any application I tend to have the following just before exiting:

CLOSE DATA
RELEASE all

*** USE THIS FOR DEBUGGING OBJECT HANGING - fires all outstanding DESTROY()
CLEAR ALL
*** END

This will do a forced release of all references.

If you want to find out what's not been released at this point you can put SET STEP ON before the CLEAR ALL and then step into the code. You should end up in the Destroy() of any object that hasn't been released yet (if there's code in there) which is a great way to see what's not releasing.

+++ Rick ---




>I have a small program and having difficult time figuring out how to remove the process for the application when it is closed.
>
>Each time the exe is run and closed, the process for the exe remains in the process list each time it is run
>
>Thanks in advance