Article ID: 197103 - View products that this article applies to.
This article was previously published under Q197103
Moderate: Requires basic macro, coding, and interoperability skills.
When you move to the next record on a form or close a form, Microsoft Access automatically saves any changes that you have made to the current record. This article shows you how to use a BeforeUpdate event procedure to prompt you to verify the save operation before Microsoft Access will continue.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
CAUTION: If you follow the steps in this example, you modify the sample database Northwind.mdb. You may want to back up the Northwind.mdb file and follow these steps on a copy of the database.
This example uses the BeforeUpdate event procedure in the Customers form to prompt the user to confirm changes before Microsoft Access will save the record: