The fact is, I give my users a choice to a number of things in the Options dialog. For example, one option is "See save messages". Another is "Prompt to Save". This applies when the user edits the record then moves to the next or closes the form. If the user chooses not to see these dialogs, then I force a save when the record pointer moves or the form closes. But, I leave it up to the user....much better solution than forcing one way or the other on them.

I think this is the best approach. Don't make the decision for the user, but allow them to decide for themselves.

As for the Save button, it is there on my forms...users have gotten use to a save button. Not just my applications, but all apps. For example, I often fire up Word to crank out a quick letter, etc. I have no intention of saving it. How is Word supposed to know this? I would find it MUCH more annoying for Word to save everything I wrote, and then I have to delete it if I don't want to save it.

With all due respect Craig, we as VFP programmers generally don't write Word Processing applications ;-) Have you ever fired up VFP to crank out a quick table, and added records without intending to save them? Database applications are a completely different animal. (As an aside, Word couldn't do this anyway, unless it generated a random filename, or made an 'intelligent' guess at a name.)