VBA AfterUpdate event (1 Viewer)

[Isaac]

I think he's use a control's AfterUpdate event also but when you manipulate a control using VBA, that control's events don't fire so that may be what is causing the disconnect. In that case, the code needs to move to the form's BeforeUpdate event or you need to do something like separate the code you want to force to run into a separate procedure and call it from the two events.

this is one thing I hate when going in between access and excel vba. in excel, programmatically modifying a control does fire its events, unless you set Application.EnableEvents=False (then set back to true afterwards), gets really thorny!
so it's an annoying difference and i wonder why MS did that differently between the two

 

[Gasman]

Different teams. Left hand not knowing what the right hand is doing.

 

[The_Doc_Man]

so it's an annoying difference and i wonder why MS did that differently between the two

That might be the wrong question. Access and Excel were "acquired" by Microsoft back in the really early days before Office was a product. MS was NOTORIOUS about co-opting other programs. (Legally, in that they bought out small designer companies who were just jumping on the PC bandwagon.) Different companies originated the designs of those two programs. The REAL question is why MS didn't "unify" the design. Possible answer: Cheaper not to.