Disabling the Auto Save Function

[stpark22]

Hello,

I've constructed a data entry form in Access 2003 that is bound to two related tables. A subform is embedded into the main form.

I enter data for the parent table into the main form and data for the child table into the subform.

By default, Access saves the record on the main form to the database if I move to the next record in the subform.

I would prefer to control when Access saves a record so I can have better control over validating the entries. Is it possible to control when Access saves a record on a bound form?

[FishVal]

Hello,

I've constructed a data entry form in Access 2003 that is bound to two related tables. A subform is embedded into the main form.

I enter data for the parent table into the main form and data for the child table into the subform.

By default, Access saves the record on the main form to the database if I move to the next record in the subform.

I would prefer to control when Access saves a record so I can have better control over validating the entries. Is it possible to control when Access saves a record on a bound form?

Hi!

You can handle Form BeforeUpdate event.
An example below will disable saving to db at all.

Private Sub Form_BeforeUpdate(Cancel As Integer)
Me.Undo
End Sub
 

[missinglinq]

You're right! The example given will disable all saving to db, but what's the point of having a database that you can never save a record to?

When you leave the record (to go to the subform) you have two choices, either save the record or dump it. If you need to do data validation, you need to do it at this point, using, as pointed out, the Form_BeforeUpdate event. You cannot enter data on the main form, freeze it, so to speak, go to the subform and then come back to it!

[FishVal]

You're right! The example given will disable all saving to db, but what's the point of having a database that you can never save a record to?

When you leave the record (to go to the subform) you have two choices, either save the record or dump it. If you need to do data validation, you need to do it at this point, using, as pointed out, the Form_BeforeUpdate event. You cannot enter data on the main form, freeze it, so to speak, go to the subform and then come back to it!

Right. This is what I've pointed out.
Sure that BeforeUpdate should contain more useful code, e.g. data validation, confirmation message etc. I've given an idea only.

By the way, setting Cancel=True in BeforeUpdate handler causes an interesting but useless effect when moving to subform:
focus is moved to subform,
record in mainform stays unsaved and never got focus again :-/

[stpark22]

FishVal & missingling,

Thank you for responding. Now I realize the this approach is not a pratical one. missingling,
Thank you for pointing out how the records are treated when you leave the main form. I wasn't aware that there were only two options at that point: save or dump. I was naively under the express that the records can be frozen while navigating through each form.

Thanks again.