Main form AfterUpdate event

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

rferrari27 - 27 Apr 2005 16:50 GMT

Hi all,
I have a main form (say MF_1) with a subform (say SBF_2);
MF_1 and SBF_1 are linked together.
In SBF_1 there is a comboBox field: whenever its value is changed,
the afterUpdate event fires ( both field and subform events).
As a consequence of that, I would like the afterUpdate event of
MF_1 to fire as well, but this does not happen.
I have noticed that the afterUpdate event of MF_1 fires only if a field
of the main form is changed, but it does not fire as a consequence of a
change in the subform.

Can someone tell me why the afterUpdate event of MF_1 does not fire?
Is there a way to either make it fires or to invoke the afterUpdate
event of main form?

Thanks in advance for any responses.
Roberto

Reply to this Message

Lynn Trapp - 27 Apr 2005 18:15 GMT

I'm not sure what you are trying to do, but what you are seeing is intended
functionality. There is no reason for the AfterUpdate event of your main
form to fire if nothing is being updated on THAT form.

Signature

Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html

> Hi all,
> I have a main form (say MF_1) with a subform (say SBF_2);
[quoted text clipped - 13 lines]
> Thanks in advance for any responses.
> Roberto

Reply to this Message

rferrari27 - 28 Apr 2005 11:08 GMT

Thank you!
I did not know that events are not propagated through forms.

In my personal opinion, if a subform "belongs" to a main form (with its
information)
and something is updated in the subform, it means the information in the
main form are changed, thus an action could be taken in the main form as well.
Final user does not distinguish between main form and subforms.

However, my idea was wrong and I am happy to learn a bit more!
Best regards,
Roberto

> I'm not sure what you are trying to do, but what you are seeing is intended
> functionality. There is no reason for the AfterUpdate event of your main
> form to fire if nothing is being updated on THAT form.

Reply to this Message