LInked Forms and Before Update event

[JB]

In Access XP, I have two forms that open together. The first one calls
the second and sets the filter condition. The process of switching
between the forms is making the BeforeUpdate event trigger on the
second form. I do not like this behavior but, based on what I have
researched so far, I think this behavior is unavoidable. Am I correct?

How can I determine in the BeforeUpdate event if the user actually did
anything to the record since Me.Dirty is always True? How can I tell If
the user is trying to add a new record in the second form? How can I
tell If the user just views the record and does not touch anything and
then simply clicks another record in the first form?

 

[Rick Brandt]

In Access XP, I have two forms that open together. The first one calls
the second and sets the filter condition. The process of switching
between the forms is making the BeforeUpdate event trigger on the
second form. I do not like this behavior but, based on what I have
researched so far, I think this behavior is unavoidable. Am I correct?

No. Switching between two separately opened forms should not trigger a save.
This is true when switching between an embedded subform and its parent form, but
not if each form is opened in a separate window.

How can I determine in the BeforeUpdate event if the user actually did
anything to the record since Me.Dirty is always True?

If BeforeUpdate is firing then some field was changed. Either by the user or by
code/macro. Do you have any such code/macro in the open, load, or current event
of the second form?

 

[JB]

Yes. I did find the code that was causing the problem. Thanks for the
response.