There are *numerous* events that will trigger Access to automatically save a
record.  The best thing to do is to realize that this is how Access works and go
with it instead of fighting it.

If you want a thin-client "detached" sort of form where nothing happens until
you tell it to then the way to achieve that in Access is to use an unbound form.
Of course doing this forces you to lose virtually all of the built in stuff that
makes Access one of the easiest and fastest tools for making database
applications with.

A record is saved when you navigate to another record unless you
specifically prevent it from being saved.  Are you using table-level
valication to ensue all fields are filled in?  You can prevent the user from
tabbing to a new record by setting the form's Cycle property (Other tab on
the form's property sheet) to Current Record.  But why do you want to force
users to reach for the mouse or go through the extra step of clicking the
Save button?  Navigating to a new record accomplishes exactly the same thing
as explicitly saving the record with a command button.

As others have said, it's best to work with the grain and allow the
record to be saved automatically. Using a combination of "required"
fields, field- and table-level validation rules, and maybe VBA code in
the BeforeUpdate events of your form and its controls, you can ensure
that the users can't save incomplete records.

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.