How To Not Update When Closing Form In Access

Confirm Changes using the Before Update Event

When creating the user interface in Microsoft Admission, the database designer should always exist looking at ways to simplify the data entry process, prevent bad data from getting into the database or ask for confirmation when changes take been fabricated to existing data.

This article concentrates on changes made to existing data, and provides the user with a confirmation pick when modifying information in a Microsoft Access class.

If we accept the post-obit case Microsoft Access form, and view the data that is currently entered into each control in the form:

Form displaying the original data in the record.

If the database user makes any changes to the electric current record, we would similar to pop upwardly a message box, confirming that the user is sure that they wish to make these changes before moving to a different or new record.

To exercise this, we demand to add a procedure to the Earlier Update upshot of the Microsoft Admission form. The BeforeUpdate result occurs before changed information in a control or record is updated.

The BeforeUpdate outcome applies simply to controls on a class, not controls on a report.

The BeforeUpdate issue does not apply to option buttons, check boxes, or toggle buttons in an option grouping. Information technology applies merely to the option group itself.

Using the following code, we tin can display the bulletin box to the user, request them to confirm if they would like to make the changes or not:

Private Sub Form_BeforeUpdate(Abolish Equally Integer)  'Provide the user with the selection to save/undo 'changes made to the record in the form      If MsgBox("Changes take been made to this tape." _         & vbCrLf & vbCrLf & "Do you want to save these changes?" _         , vbYesNo, "Changes Made...") = vbYes Then             DoCmd.Salvage         Else             DoCmd.RunCommand acCmdUndo     Cease If Terminate Sub

When changes are made to data in the class, and the user tries to move to a new/next record, or they endeavour to shut down the course they will be presented with the following message box:

Message Box displayed when changes are made to information in the record (note change made to the Request Cost data in this example)

If the user chooses Yes from the message box, the code will run the post-obit argument, saving the new data:

DoCmd.Save

If the user chooses No from the Access message box, the lawmaking volition run the following statement, undoing any changes fabricated to the information: