I'm thinking of using the Active/Deactive events of a form to just set Me.Dirty = False forcing the record to save when the user goes on to another window. Would this solve my dilemma? Can anyone offer me some guidance?
Hi HTHP,
I don't think there is a general recipe to handle these things.
In my applications I have about the same situation. A lot of form-handling can be "controlled" by a good use of Dialog forms.
Because I can "walk" from one form to an other using the existing relations bidirectional, it is possible that an open form a second time is called. Access will bring that form to the foreground. In the command to open a form I therefore will first
close the form with the same name, and then open the form again. It makes the form more dynamical.
To even make it more dynamical, changed data is saved on the exit of a control. So whenever you go to a new form, data is already saved.
But I think there are more scenarios.
Imb.