>Normally, that's exactly what I do. If a user hits Exit, they want to Exit, so I Exit......and revert the tables. If a user wants to save the data, that's what the Save button does. The user is the power here, I just do what they want. So OK, I'm working this app where everyone thinks that they are going to do work, and hit exit.....by mistake....although the Save and Exit buttons are separated by considerable screen real estate. I don't buy it but hey, they're writing the checks so they can get whatever they want. Looks like I'll be building a message on Exit to "ask" if the user wants to "Save" the data.

It's a tough call...We've even contemplated going the other way, with automatic save on exit (I've done this in my timesheet app, with nary a complaint)...hate to get stuck on such an issue, but we have several teams involved and another meeting scheduled on this issue (groan) (s), since we have to standardize it for all current/future systems...