Yup, yup! Asking the user to confirm what they are doing is annoying to the user in the long term.
>>Or only have it fire if there are uncommitted changes, like Office does....
>
>Of course, that's another story, and that query is fine. In this case, it doesn't appear to be relevant. That message orignated in mainframe days, when logging back in was a big issue. I remember in college, using dumb terminals, with the system overburdened, often if you logged out, you might have to wait an hour or more to get back in after enough users got off. There, the message made some sense...
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05