J
JerryK
Hi,
I am wondering what is the proper way to terminate an MDI app that has
"dirty" forms.
In my case, the child form is editing some data. If the user presses the
"X" button on the main form, the code I have is
parent_Closing (...) handles MyBase.Closing
Application.Exit()
End Sub
When the Application.Exit()ethod runs it causes the the closing event to run
in the child form. The chid's Closing event brings up a dialog that display
a message about lossing your changes and gives the user the options to Save
changes and close, abandon changes, or cancel the close. If they select the
cancel close method, e.cancel is set to True. I assumed that this would
cause the Application.Exit to cancel, but it apparently does not. So the
question is what is the proper way to give the user a chance to abort the
close?
Thanks,
Jerry
I am wondering what is the proper way to terminate an MDI app that has
"dirty" forms.
In my case, the child form is editing some data. If the user presses the
"X" button on the main form, the code I have is
parent_Closing (...) handles MyBase.Closing
Application.Exit()
End Sub
When the Application.Exit()ethod runs it causes the the closing event to run
in the child form. The chid's Closing event brings up a dialog that display
a message about lossing your changes and gives the user the options to Save
changes and close, abandon changes, or cancel the close. If they select the
cancel close method, e.cancel is set to True. I assumed that this would
cause the Application.Exit to cancel, but it apparently does not. So the
question is what is the proper way to give the user a chance to abort the
close?
Thanks,
Jerry