Just because something is a user requirement doesn't mean it's a good idea. I usually explain these types of issues to the user when they state the "requirement". If they still insist, I go with it.

I'm not very familiar with WinForm event sequence, so I don't have a better idea for you.


>I don't disagree with you. However, the users want to make sure that if anything that has been changed, they are given the option to save their changes. Their screens have up to 10 tabs (user requirement, not my idea) on them with many tables that are affected. I have code that checks all the Close buttons and the leave events on the tab pages. However, the X in the control box apparently bypasses the leave event for the tab pages so none of those automatic saves fires. My thought was to eliminate the X of the control box so they have to use the Close button. I suppose the alternative is to add code to the the closing event to check for changes in each and every table. That just seems like a maintenance nightmare.
>If you have a better idea, I'd love to hear it. Thanks.