>I have a standalone VFP application that exits properly when the user clicks the Exit button. However, under two special circumstances the program closes down but remains in memory, as seen in the task manager. I don't know how to prevent this from occurring. (It takes several attempts at closing the application through the task manager in order to remove it.)
>
>Failure to exit memory case #1) During the Init of the first form (called from the main prg) I have a test for a configuration setting in the application's INI file. If the setting does not exist the form displays a messagebox and then closes automatically with a RETURN .F.
>
>Failure to exit memory case #2) If the application is run from the Windows Scheduler, passing a parameter that tells the app to run in automated mode, it will run the procedure and close down the application automatically when it finishes. In this case I am doing a thisform.cmdExit.click upon completion of the procedure.
>
>FYI: I have a READ EVENTS statement in the main prg just after my DO FORM ... statement. In the DESTROY event of the form I am doing a CLEAR EVENTS.
>
>Any ideas would be greatly appreciated.

The first simplest thing which comes to mind is to check, if Form's Destroy always fires? IOW, put some wait window here (or debug output, or log file). I would start from here.