Close a Form and Subform without saving either

[whisp0214]

This would seem to be simple, but i have looked for an answer that works and haven't come up with anything. Here is the setup.

I have a keyword search box and command button on the main form to filter the subform, along with a save and cancel button. The goal is for any employee to search an order using the search function and make an edit on the subform when necessary, then save it and close the form. However, if an unwanted change is made and the cancel button is hit, the changes are still saved. The dirty function works fine controlling the main form with undo in the code, but they do not translate to anything done on the subform. Below is my code for canceling and closing information on main forms. Can someone help me fix this to also affect the subform?

If Me.Dirty = True Then


DoCmd.RunCommand acCmdUndo
DoCmd.Close acForm, Me.Name
Else
DoCmd.Close acForm, Me.Name
End If

Thanks,

Garret

[Missinglinq]

When you move from the Subform to the Main Form (where your buttons are, if I read this correctly,) the Subform Form Record is automatically saved...that's how Access works. You need your Save/Dump buttons on the Subform, if it's Subform Records you're dealing with.

You can't have Command Buttons on Datasheet View Forms, as most Subforms are displayed, and the usual approach is to have the Subform in Continuous View, which can have Command Buttons, tweaked to look like a Datasheet View Form, if that's your preference.

Linq ;0)>

[whisp0214]

When you move from the Subform to the Main Form (where your buttons are, if I read this correctly,) the Subform Form Record is automatically saved...that's how Access works. You need your Save/Dump buttons on the Subform, if it's Subform Records you're dealing with.

You can't have Command Buttons on Datasheet View Forms, as most Subforms are displayed, and the usual approach is to have the Subform in Continuous View, which can have Command Buttons, tweaked to look like a Datasheet View Form, if that's your preference.

Linq ;0)>

Thanks for the confirmation. That was what I was thinking, but I really hoped there was a VBA solution to it.

[CJ_London]

but I really hoped there was a VBA solution to it.

investigate begintrans, committrans - might do what you want