CANCEL, or just returning from the main program (with or without a RETURN statement) should be OK. On the development machine, you return to the command window (which is the main reason I don't use QUIT); this is an important advantage of not using QUIT. However, your program might keep files open, so you may want to use CLOSE ALL and CLEAR ALL at the end.
When you finish working in
development mode, use QUIT to quit VFP, or just press Alt-F4.
>David:
>
>I tried ending without a quit (or a return), and did not get the unwanted message.
>Thanks.
>
>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?
>
>Dennis Lytle
>Princeton PC Systems
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
