I've got a form used as a modal dialog that has a QueryUnload event used
to validate the data entered by the user.  If the data is not valid,
a MsgBox is displayed and Cancel is set to true.

If I use the Close menu option from the control menu, or unload the form
in the code, the QueryUnload event fires and I see my (optional) MsgBox
telling me some data is not correct on the form.

However, if I run the same program as a standalone-exe and use the Windows'
Task Manager to kill the program, the program just beeps (even though
there is no MsgBeep call in the program) and no MsgBox is displayed, yet
the program stays up (i.e., Cancel is being set to true).

I'm at a loss to understand what is happening here.  Any ideas?

Kevin
--
Kevin W. Hammond

says:

I would think TASKMAN is not being so polite as to send a
WM_QUERYENDSESSION but simply gets to the point and sends a WM_ENDSESSION
directly.

So your task doesn't get politely asked if it wants to terminate.

It is{*filter*} around because you don't have an END statement in your
unload event; in VB design mode that doesn't matter but as an .EXE it
certainly does.