I have a data entry form with a 'Save' button that allows the user to save a
new record. There is code tied to the form's Before Update event that checks
to see if the record is complete before saving.  If not, the user is
prompted to save anyway or cancel.

All works well except if the user tries to cancel. The cancel will take
place but an annoying message pops up saying "The setting you entered isn't
valid  for this property" or "The Run Command Action was cancelled."

The actual message depends on the code I use to save the record.  I tried
three methods:
    DoCmd.DoMenuItem.......
    DoCmd. Run Command.acCmdSaveRecord
    If Me.Dirty Then Me.Dirty = False

All of these methods return messages when cancelled.

Does anyone have a suggestion on how I can cancel a save gracefully?

Thanks,
Dave

[snip]

There are several strategies that you may want/need to use in combination,
including trapping errors at in the form's OnError event. (There are some
errors you can't trap there, though, as you no doubt have found out.) Here
is one crude tactic that relies on the SendKeys action. It has helped me in
non-production-quality apps. Ace programmers, please don't flame me for this
;-)

    'test for dirty record
    If Me.Dirty Then
        strM = "You are in the midst of adding/editing this order. "
        strM = strM & "Click OK to proceed without saving changes."
        intR = MsgBox(strM, vbOKCancel, "Order Add/Edit in Progress")
        If intR <> vbOK Then
            GoTo Exiter
        End If
    End If

    'If okay to abort,
    'get rid of that damn pencil
    SendKeys "{ESC}", True
    SendKeys "{ESC}", True

    'close the form or do whatever

Tony Scilipoti
****************
Applications Development Lead
Brigham Surgical Group
Brookline, Massachusetts USA

Thanks Tony.

I also found an example in Balter's Mastering Access:

    DoCmd.CancelEvent

Dave
-------------------

There's also docmd.runcommand acCmdUndo.

Not the right way, but it will work....

Example below is the code that is "automatically" placed in a close button.
You can simply replace the
"On Error GoTo Err_cmdExit_Click" with "On Error Resume Next".  This would
allow processing;
------------------------------------------------------
On Error GoTo Err_cmdExit_Click

WarnOff  'added as part of functions noted below
DoCmd.Close
WarnOn  'added as part of functions noted below

Exit_cmdExit_Click:
Exit Sub

Err_cmdExit_Click:
MsgBox Err.DESCRIPTION
Resume Exit_cmdExit_Click
------------------------------------------------------

better yet, create these two functions:
------------------------------------------------------
Function WarnOff()
' Turn Comfirmations Off
Application.SetOption "Confirm Action Queries", False
Application.SetOption "Confirm Document Deletions", False
Application.SetOption "Confirm Record Changes", False
DoCmd.SetWarnings False
End Function
------------------------------------------------------
Function WarnOn()
' Turn Comfirmations On
Application.SetOption "Confirm Action Queries", True
Application.SetOption "Confirm Document Deletions", True
Application.SetOption "Confirm Record Changes", True
DoCmd.SetWarnings True
End Function

------------------------------------------------------

This will "quiet" the messages you see, but not true errors.

Regards,

Todd

Dave,

Looks like there are lots of alternatives for this based on all the posts.  I
had the same annoying warning box, and below is the code I added.

  On Error GoTo Err_cmdDelete_Click

..your code to validate user entries..

Exit_cmdDelete_Click:
    Exit Sub

Err_cmdDelete_Click:
    If Not Err.Number = 2501 Then       'Err 2501 is raised from cancel of
DoCmd action.
        MsgBox Err.Description
    End If

    Resume Exit_cmdDelete_Click

End Sub

David

- - - - - - - -

David

I find it easier to type the following.  Works well, less keystrokes... <g>

me.undo

Gary :)