Hi Ed,
You almost got me. According to the help and my testing, Release never fires if QueryUnload fires.
Q: Is there anyway to get the release event to fire other than explictly calling it?
Q: If you don't use QueryUnload, how do you do it, or did you mean something else?
>Take a look at putting something in the QueryUnload method, which fires after Release but before Destroy if some action other than something invoking the Release method or a form method issuing a RELEASE command triggers shutdown - issuing a NODEFAULT prevents the form from unloading. The ReleaseType property is set before the QueryUnload fires, clicking the close control on the form sets ReleaseType to 1, so that's trappable. I've never used this approach to prevent things from happening, but the controls and properties are still intact before the code in Destroy fires...
Roi
'MCP' Visual FoxPro
In Rome, there was a poem.
About a dog, who found two bone.
He lick the one, he lick the other.
He went pyscho, he drop dead!