Although I haven't quite gotten to the point where this has been implemented, this seems to be the inevitable result of the direction I'm taking now:

1.) Edit on demand
2.) Confirm save message with checkbox(ala Netscape) "Show this box next time". This flag would need to be reset each time the app is fired up but would be retained for the duration of the current session. (I've also considered disabling the checkbox for new users)
3.) Revert Edits button with messagebox confirm.

This approach allows power user speed and gives some protection from doing thing accidentally.

For vital information that wouldn't be changed on a regular basis, it might be worthwhile to put some field-level controls either in the DBC or in the field control.

One note. IMHO, the Deleted Folder in WIN95 and WINNT is a pain in the neck, so I tend to do file manipulation from a DOS prompt. But over the last few years, I can think of no less than 4 occaisions where I deleted the wrong file, or worse, wrong directory and I had no other undelete utility running.

The point is, even power users make mistakes, and with every chance we get to improve usability, we must make every consideration to ensure that we don't provide the ability to accidentally corrupt or lose large chunks of data.