David,

Dennis is talking about run-time in his initial message. I always thought that QUIT is the safest way to clean-up and close the application. I am surpised to learn that it may not be. Would you please share the info you have on what QUIT is doing (or not doing properly)?
BTW, my suspicion after reading Dennis' initial post, was that there is an ON SHUTDOWN CANCEL statement active which cancels the procedures on QUIT.

TIA


>Dennis,
>
>>I have always QUIT because of this message in the VFP Help files:
>>
>>>>Always use QUIT to terminate a Visual FoxPro session. If you turn the computer off without issuing QUIT, open files may be damaged and data lost, and temporary work files that would normally be deleted may be left on disk.<<
>>
>>I guess the burden is on "good programming practices" to see that all files are properly closed and/or deleted. What about instantiated objects, etc.
>>Do they need to be explicitly released?
>
>Well your app as part of it's shutdown ought to be doing things like telling your app object to close down all forms, setting your global objects to .null. to terminate their existence, CLOSE DATA ALL, etc. to make sure your app is shutting down in a controlled manner.
>
>But when your main does a return VFP will do it's own thing to make sure it closes files.
>
>That help topic is not written very well, perhaps you'd like to click the feedback item and make a couple of constructive changes for the VFP documentation team to review, they really do have a directive to get the docs more useable for people.