Microsoft KB Archive/289895

= ACC2002: BeforeUpdate and AfterUpdate Properties Are Not Working =

Article ID: 289895

Article Last Modified on 11/6/2003

-

APPLIES TO


 * Microsoft Access 2002 Standard Edition

-



This article was previously published under Q289895



Moderate: Requires basic macro, coding, and interoperability skills.

This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).

For a Microsoft Access 2000 version of this article, see 201088.



SYMPTOMS
The macro or function that is attached to the BeforeUpdate or AfterUpdate property of a bound control does not run when expected.



CAUSE
The BeforeUpdate and AfterUpdate events of a bound control are not triggered if the bound control is first modified by a macro or by code.



RESOLUTION
You can work around this behavior by causing the macro or the code that modifies the bound control to manually trigger the event that is pointed to by the BeforeUpdate or AfterUpdate property of the bound control.



Steps to Reproduce the Behavior
 Open the sample database Northwind.mdb.  Create the following macro, and name it TestCityForNull:   Macro Name       Condition        Action -  TestCityForNull  IsNull([City])   MsgBox ...             CancelEvent

TestCityForNull Action Arguments --  MsgBox: Message: City Is A Required Field!   Create the following macro, and name it SetCityToNull:   Macro Name        Action --  SetCityToNull   OpenForm SetValue

SetCityToNull Action Arguments ---  OpenForm Action: FormName: Customers View: Form

SetValue Action: Item:[Forms]![Customers]![City] Expression: Null  Open the Customers form in Design view, and then select the TestCityForNull macro in the BeforeUpdate property of the City control.</li> Run the SetCityToNull macro. Note that it successfully blanks out the City field (you can press ESC twice to get it back). If the BeforeUpdate event of the control had been triggered, the TestCityForNull macro would not have allowed the field to be blank.</li> Try to blank out the City field manually. Note that the TestCityForNull macro is triggered and displays the following message:

City Is A Required Field!

</li> Do not save changes when you close the Customers form.</li></ol>

Additional query words: before after update ui prb

Keywords: kbprb KB289895

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.