By simple way is by using Access as it was intended to be used, with Bound Forms! When a Form is Bound, the Record is committed to the Table, automatically, as soon as the user moves to another Record, closes the Form or closes Access itself.
Don't know why you're apparently using Unbound Forms, here. The usual justification for this is the belief that Unbound Forms are necessary in order to do data validation before "committing" data to a Table, and this is simply not true!
Any "checks" you need to do before saving the data can be done using the Form_BeforeUpdate event of a bound form and Cancel = True to stop the saving of the record until missing/erroneous data is dealt with!
A big part of the reason to use Access for database development is the speed with which it can be created, using Bound Forms. Several developers I know, experienced in both Visual Basic database development and Access development, estimate that development using Unbound Forms by experienced developers takes two to three times as long as it does when using Access and Bound Forms.
If you insist on using unbound forms, you'd be far better off using a straight VB or C++ front end with a SQL Server or Oracle back end.
- You can create an EXE file which gives total protection to your code/design
- You can distribute the db to PCs without a copy of Access being on board
- Your data security is far, far better than anything you can do in Access
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007