Me.Dirty not catching

[Ashe]

I have a bound form with code to undo a record if the user closes the form without saving the changes. For some reason, even after typing and tabbing through controls, Access isn't registering that the form is dirty. (Or I'm not grasping the meaning of "dirty"). The form is opening to a new record should not save the record if the user doesn't say "Save"...

My code is below:

Private Sub Form_Close()
    If Me.Dirty Then
        DoCmd.SetWarnings False
          DoCmd.RunCommand acCmdUndo
        DoCmd.SetWarnings True
    Else
        MsgBox "didnt catch"
    End If
End Sub

Is this because I'm adding a new record and not actually changing an existing record?

[TheShabz]

See if this helps you a bit.

http://msdn.microsoft.com/en-us/library/bb240721.aspx

[Ashe]

According to this link, the record is dirty if a user has made changes. If the user is adding a new record, if this considered "dirty"? The link doesn't address new records.

Also, this command (If Me.Dirty) does catch on in another sections of my code. That makes me believe that Dirty refers to changes to an existing record and creating new records.

However, a new record is definitely being made, and the If Me.Dirty command is not triggering as "True". I'm wondering if this has to do with the 60 second refresh of records, but the amount of time since the record was first created also seems to have no impact.

[boblarson]

It helps if you understand the order of events.

If you go to this page:
http://office.microsoft.com/en-us/ac...005186761.aspx

and then to this part:

Order of events for forms and subforms

It will show that the Unload event occurs before the Close event. So the Unload event is when the recordset is unloaded from the form. So, if the form was dirty, it already went through the form's BEFORE UPDATE event and then the recordset has been unloaded and then the form closes. So the form can't be dirty when the form close event occurs.

[Ashe]

Thank you Bob! That is a very helpful and interesting link!