Can I turn off the Access methods for saving a record?

  • Thread starter Thread starter John Doe
  • Start date Start date
J

John Doe

I would like to be able to force the user to be able to save a record
ONLY by using the SAVE button I have provided on the form. I have
either disabled or set not visible all the form items that save the
record (such as the navigation buttons).

However, there are two other things: (1) the menu item under "Records"
menu as well as the SHIFT-ENTER keys that correspond to that menu
item, and (2) using the TAB key cycles through all the controls and
when it gets to the last one it saves the record.

I would like to turn OFF all of the ways Access saves the record and
force the user to use the SAVE button on the form. That way I can be
sure all the code gets executed on save.

Any way to do that?

Or should I think of a different way to do things?
 
Unbound forms will allow you to do that. You populate all the controls
on your form using a recordset upon selecting a record, and update the
recordset with the controls' values upon saving. Not a trivial
undertaking.


I would like to be able to force the user to be able to save a record
ONLY by using the SAVE button I have provided on the form. I have
either disabled or set not visible all the form items that save the
record (such as the navigation buttons).

However, there are two other things: (1) the menu item under "Records"
menu as well as the SHIFT-ENTER keys that correspond to that menu
item, and (2) using the TAB key cycles through all the controls and
when it gets to the last one it saves the record.

I would like to turn OFF all of the ways Access saves the record and
force the user to use the SAVE button on the form. That way I can be
sure all the code gets executed on save.

Any way to do that?

Or should I think of a different way to do things?
Click to expand...


**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
Jack has suggested one of the standard approaches. I usually go at it
from a different angle: lock the form (using its AllowEdits property or
by locking individual controls where needed) and then provide an Edit
button that unlocks it.

That takes care of accidental edits; and code in the form's BeforeUpdate
event procedure can do whatever needs to be done before the data is
saved.
 
Back
Top