Using Me.Dirty in a BeforeUpdate event procedure.

[MatthewGrace]

I'm having difficulty with a common feature of Access programs: a BeforeUpdate confirmation to commit changes, where if the user selects "No (I don't want to commit changes)", the control values go back to their previous value. The issue I have while building the said feature is found in the "me.Dirty = false" line. I normally don't use the "dirty" feature and I cannot figure out why it is tripping Error 2115, Saying that my code in this BeforeUpdate procedure is preventing Access from saving the data to the field.

My trouble is that if I don't use the .dirty line, then inevitably the user will try again to move the record selector elsewhere, only to be prompted endlessly with this same Messagebox asking if they want to commit changes they've already said no to previously. Thanks for any insight.

[June7]

Me.Dirty = False causes the data to save or at least try to. You don't want that code in this event.

Try Me.Undo instead. And should not need the control looping.

http://www.blueclaw-db.com/access_ev...foreupdate.htm

[Missinglinq]

Me.Dirty will always be True, in the Form_BeforeUpdate event; how can it not be? If the Form wasn't dirtied, there would be no reason to Save the Record, and the event would never be executed!

All you need to accomplish your goal is

Private Sub Form_BeforeUpdate(Cancel As Integer)
 If Not Me.NewRecord Then
  If MsgBox("Routing details of this skid have been altered.  Commit?", vbYesNo + vbQuestion, "Skid Manager - Commit Changes") = vbNo Then
   Me.Undo
  End If
 End If
End Sub

Linq ;0)>

[MatthewGrace]

Thank you both for your replies. solved.