I forget now what we're talking about. :) If it's the message to confirm that, through some extraordinary combination of circumstances and pure blind luck, data was actually saved when the user clicked Save, I wouldn't devote a particle of development time to it.

No, I would never present a dialog box confirming a save that is the result of a user clicking on the save button...unless the user specifically asked for this function, and I couldn't talk them out of it.

What I was referring to is the dialog that typically appears when a user tries to go to another record, or close the form/ampplication. This is usually something along the lines of; "Changes have not been saved, would you like to save them?"

That includes designing the message box (and localizing it), the checkbox to turn it off, the registry setting to store that it has indeed been turned off, and the dialog box item that lets you turn the stupid thing back on again. :)

I would venture to say, that in the context of building an entire application, this work would be the least of my worries.