Can you stop a form from updating the database when exiting?

[Birky]

How can I stop a form from updating the database when a user closes the form? I have a form which is used for referencing, additions, and modifications but every time the form is closed with no modifications the entry which is being displayed is then stored in the database causing duplicates. My hope is to only allow additions and or modifications if they select the proper command button. If they just close the form I would like nothing stored to the database. Because the form is used for reference I have the Data Entry set to NO. Is there an easy way to do this?

Please help…
Birky

[NeoPa]

In the OnClose event procedure for your form, include something like :

Me.Dirty = False

I believe the following works too :

Call Me.Undo

[Birky]

This works if the code is behind a control object which is calling the DoCmd.Close function but if the Forms CloseBox (upper X on the forms border) is used the record is saved before the form is closed. Any idea how I can get this to stop updating and just close the form straight away? Note I have tried the both the Undo and Dirty options within the forms OnClose event and neither seem to stop the saving if this X is selected.

Private Sub CmdExit_Click()
On Error GoTo Err_CmdExit_Click
 
    Call Me.Undo
    DoCmd.Close
 
Exit_CmdExit_Click:
    Exit Sub
 
Err_CmdExit_Click:
    MsgBox Err.Description
    Resume Exit_CmdExit_Click
 
End Sub
 

[MMcCarthy]

Try putting this in the On Close event.

 
Private Sub Form_Close()
    ' Undo the current record
    DoCmd.DoMenuItem acFormBar, acEditMenu, acUndo, , acMenuVer70
End Sub
 

For some reason Dirty doesn't read True in the On Close event.

Mary

[NeoPa]

Mary,
Do you know why Me.Undo (or even Call Me.Undo) doesn't work?

[MMcCarthy]

Mary,
Do you know why Me.Undo (or even Call Me.Undo) doesn't work?

Something to do with the form losing focus in the close event. Same problem with Me.Dirty.

[MMcCarthy]

Something to do with the form losing focus in the close event. Same problem with Me.Dirty.

For the sake of experimentation probably should be tried as

 Forms!frmName.Undo

[NeoPa]

Thanks.
So, when you use the DoCmd form it passes control out of it's own module to do the job. That makes a sort of sense I suppose.

[Lysander]

This works if the code is behind a control object which is calling the DoCmd.Close function but if the Forms CloseBox (upper X on the forms border) is used the record is saved before the form is closed. Any idea how I can get this to stop updating and just close the form straight away? Note I have tried the both the Undo and Dirty options within the forms OnClose event and neither seem to stop the saving if this X is selected.

I would disable the Forms CloseBox using forms properties and add my own Close button. That way, I can make sure the form is closed the way I want it to be closed. Having said that, I had a similar problem problem, with records being saved before I was ready to save them and spent ages putting all sorts of fixes and traps in. Worked fine in London on a PC, but when system went live in Africa running on laptops, certain ways of pressing those rotten touchpads would save the record. Only by disabling the touchpad and using mice on the laptop would the problem go away.

[MSeda]

Birky,
aside from the discussion on how to undo the changes made on the form. I'm curious as to how it is that the duplicate record is being created in the first place. How does the user select which record to view/edit or select to add a new record. do you have a combo box or record selectors on the form or have you employeed some other method of navigation?
It seems to me, the fact that a duplicate record is being created indicates that some how the existing record the user is accessing is erroneously being populated into a new record rather than the user viewing the existing record.