>>>>I don't like using Destroy - it's too late to stop things at that point...
>>>
>>>Okay...that is a personal thing...but in this case, if I were arguing, I would contend that if we are issuing a CLEAR EVENTS, we know that we are done with this form...but I am not arguing...
>>>
>>>I am not saying that code in the QueryUnload procedure might not be needed, just that the CLEAR EVENTS could go in the Destroy procedure.
>>>
>>>Anyways, just a matter of taste.
>>
>>This is true, there's more than one way to handle it - I just prefer to keep all related exit code in one place, and the Queryunload is the optimal place for that...no need for either Release or Destroy code, then...
>
>The QueryUnload event does not occur if you issue the RELEASE command on the form in code or invoke the form's Release method.
>
>Doesn't this mean that if the user presses the button with RELEASE THISFORM in its click procedure, the form's QueryUnload procedure will NOT be performed?

In the click procedure, you just call the Queryunload, which has all the exit code in it...