Hi Greg,
The VFP program will not be released from the memory until all the objects in it are released. The change in the behavior between VFP9 and previous version could be result of fixed bug, new bug or change in behavior. Anyway, you'll have to figure out whcih object(s) is a culprit in order to fix the problem. Take a look at the David Frankenbach's article at
http://www.geocities.com/df_foxpro/qoop017.htm. You can adjust his code to dump all the object references from your app to a file for further analyzis.
Take a look also at
http://fox.wikis.com/wc.dll?Wiki~ManualGarbageCollection~VFP>I have a compiled application (.EXE) that hangs in memory after closing. I have a main program that setups up my program (shows splashscreen, logs in user, sets menu, etc.) and then executes a READ EVENTS. The menu command and ON SHUTDOWN (set in main program) both execute a UDF QuitProgram.prg. The QuitProgram.prg checks first for a modal form (if so, shutdown is stopped), then clears any modeless forms (calls RELEASE method of each form), and then a CLEAR EVENTS. This then releases the READ EVENTS in the main program which then clears the environment and quits (in an EXE a QUIT command; in an APP the development environment is restored).
>
>This program has worked without change in versions 7 and 8; now in version 9 the program appears to be quitting (the display screen is cleared); however, a view of the running processes (Task Manager) shows the program to still be present in memory.
>
>I have tried to duplicate the behavior in a test program, but it is closing properly. Any help would be appreciated.
--sb--