how to explicitly save a form

[wtolentino]

i have created a form with a field bound to a table. i want to explicitly save the data that is being entered on the form. so i added this code on the form's event on close to prevent the form from saving the data automatically when the form is closed.

If Me.Dirty Then
Me.Dirty = False
End If

it does not work it still saving the data automatically when i entered a data. i debug the code to check if the Me.Dirty is working by adding a MsgBox on top of it

MsgBox ("Me.Dirty " & Me.Dirty)

the message box is giving me "Me.Dirty False" message. i also tried using the [Form].[Dirty] still does not work. is there wrong with my code or i am doing it wrong ? please advise.



thank you,
warren

[RuralGuy]

"Me.Dirty = False" saves any changed records in a form.
If you want to "undo" and changes to a record of a form you would use the Before Update event with:

Private Sub Form_BeforeUpdate(Cancel As Integer)
    Me.Undo
    Cancel = True
End Sub

[wtolentino]

thank you it works that prevent it from automatically saving the data entered. however, the save button that i have now was not working and appears to be in conflict with the me.undo command.

i have this save button that has a macro on it

if [Form].[Dirty] then
RunMenuCommand
Command SaveRecord
En If

[davegri]

i add the code on the before update event.

Private Sub Form_BeforeUpdate(Cancel As Integer)
Me.Undo
Cancel = True
End Sub

when i entered a data on the form it is still saving the data.

Very odd. This code should prevent the form from EVER completing an update.

[RuralGuy]

As davegri stated, the code I gave you keeps you from *ever* saving a record. I did it to get you started. If you want to make it conditional then use your button to set a Boolean variable and then test for the value in the Before Update event.

[wtolentino]

thank you all. i made a tweak to the code and moved it to the form's event on close and it works.


Private Sub Form_Close()
If [Form].[Dirty] = False Then
Me.Undo
End If
End Sub

[RuralGuy]

I don't think that will do what you want. Just my $0.02.

[wtolentino]

you're right. it did not work as i test it more. the problem with the beforeUpdate is that it will prevent it from ever saving a record. my issue was that i do not want the form to be automatically saving by itself. every time i entered/update a data it saves it automatically. what i want to accomplish was only when the save button is clicked that is the time it will save the data.

[davegri]

Maybe something like this. An implementation of a variation of RuralGuy's idea in post #5. The tempvar holds the permission for the before_update to cancel or not.

Private Sub cmdSave_Click()
    On Error Resume Next
    TempVars!tvSaveOK = True
    DoCmd.RunCommand acCmdSaveRecord
End Sub


Private Sub Form_BeforeUpdate(Cancel As Integer)
    If Me.Dirty Then
        If TempVars!tvSaveOK = True Then
            TempVars.Remove "tvSaveOK"
            Exit Sub
        End If
    End If
    TempVars.Remove "tvSaveOK"
    Me.Undo
    Cancel = True
End Sub

[RuralGuy]

I'm thinking removing the TempVar may cause an issue under certain circumstances since it may not exist.

[davegri]

I'm thinking removing the TempVar may cause an issue under certain circumstances since it may not exist.

A great thing about tempvars is tolerance for nulls.
If you test a non-existent tempvar for true or false, neither is true. Null is returned.
The bad thing about tempvars is that you can use them without a Dim statement, and even if you do Dim one or not, Option Explicit will not warn you if you misspell it in code.
You may be right about "certain circumstances". That's what testing is for, and the OP is so warned.