2501 SendObject Error - Error Trapping Not Working

[Brilstern]

This question is very similar to https://bytes.com/topic/access/answe...ing-sendobject

I am receiving a 2501 error when I cancel my sendObject cmd, which I have built error checking in for. When a user cancels the sending of an email, I receive the sendObject error twice and the application freezes. Once, which is not trapped and I can click Ok, and the second time, which my error checking traps. The issue is after I click ok on my own msgbox the application freezes and I have to close it from the taskman. Am I missing something here? It has to be simple and I am overlooking it.

Sub:

Private Sub emailReport_Click()
 
'Run the Error handler "Errhandler" when an error occurs.
Dim Action As Integer
On Error GoTo ErrHandler
 
    If strReport = "" Then
 
        MsgBox "You don't have a report open, please regenerate the report", vbExclamation, "No Report Selected"
 
    Else
 
        Reports(strReport).Caption = "RMF Report"
        DoCmd.SendObject acSendReport, strReport, acFormatPDF, , , , "Emailing RMF Report", , True, "RMF Report"
 
    End If
 
    Exit Sub
 
ErrHandler:
 
              ErrorHandling strNull, Err, Action
 
              If Action = Err_Exit Then
                 Exit Sub
              ElseIf Action = Err_Resume Then
                 Resume
              Else
                 Resume Next
              End If
 
End Sub

Error Checking:

Option Compare Database
'Declared Sub ErrorHandling
Public Const Err_Exit = 0
Public Const Err_Resume = 1
Public Const Err_Resume_Next = 2
Global strNull As String
 
Sub ErrorHandling(strNull As String, ErrorValue As Integer, ReturnValue As Integer)
 
   Dim Result As Integer, ErrMsg As String, Choices As Integer
 
   Select Case ErrorValue
 
      Case 68:     'Device  not available.
 
         ErrMsg = "The device you are trying to access is either " & _
            "not online or does not exist. Retry?"
         Choices = vbOKCancel
 
      Case 75:     'Path/File access error.
 
         ErrMsg = "There is an error accessing the path and/or " & _
              "file specified. Retry?"
         Choices = vbOKCancel
 
      Case 76:     'Path not found.
 
         ErrMsg = "The path and/or file specified was not found. Retry?"
         Choices = vbOKCancel
 
      Case 94:     'No Value Selected.
 
         ErrMsg = "Please select a value."
         MsgBox ErrMsg, vbOKOnly
         ReturnValue = Err_Exit
         Exit Sub
 
      Case 2501:   'Action Canceled
 
         ReturnValue = Err_Exit
         Exit Sub
 
      Case Else:   'An error other than 68, 75,76, 94, 2501 or 3022 has occurred
 
         ErrMsg = "An unrecognized error has occurred ( " & _
            Error(Err) & " ). The macro will end."
         MsgBox ErrMsg, vbOKOnly
         ReturnValue = Err_Exit
         Exit Sub
 
   End Select
 
   'Display the error message.
   Result = MsgBox(ErrMsg, Choices)
 
   'Determine the ReturnValue based on the user's choice from MsgBox.
   If Result = vbOK Then
      ReturnValue = Err_Resume
   Else
      ReturnValue = Err_Exit
   End If
 
End Sub
 

So to describe the steps.

I open a report to print preview and a small management form is opened up that allows me to email/save/print the form.

From that form I press an email button.
The email is generated and then the email pops up to allow the user to edit the email. If the user send the email. It works great.
If the user exits the email window they receive an initial error:

Title: The SendObject action was canceled.
Message: You used a method of the DoCmd object to carry out an action in visual basic, but then clicked cancelling a dialog box.
For example, you used the close method to close a changed form, then clicked cancel in the dialog box that asks if you want to save the changes you made to the form.

After I click ok, my error handling message appears for 2501 "Action Canceled"

Once I click ok here, there application is frozen and must be closed via taskman.

[Seth Schrock]

Nothing is jumping out at me right away for why is is failing. Have you tried stepping through your code while checking values to see which line of code is locking up the program and what the variable values are at the time?

[Brilstern]

Thanks for the look Seth. I have not, but I will do so today and report back.

[ADezii]

This is just my personal opinion, but I feel as though you need to capture Error 2501 at the point of origin (Click() Event of EMailReport Command Button) and NOT in a Customized Error Handling Routine. A simple execution of the displayed Code segment should prove/disapprove my idea. If I am incorrect, I do apologize for wasting your time.

Private Sub EMailReport_Click()
On Error GoTo Err_EMailReport_Click
 
DoCmd.SendObject acSendReport, strReport, acFormatPDF, , , , "Emailing RMF Report", , True, "RMF Report"
 
Exit_EMailReport_Click:
  Exit Sub
 
Err_EMailReport_Click:
  Select Case Err.Number
    Case 2501
      'Ignore, no Message required (User Cancelled)
    Case 68, 75, 76, 94, 3022
      MsgBox Err.Description, vbExclamation, "Error in EMailReport_Click()"
    Case Else
      MsgBox "An Unrecognized Error has occurred!", vbExclamation, "Error Unrecognized"
  End Select
    Resume Exit_EMailReport_Click
End Sub

[Brilstern]

Checking now, never a waste of time ADezii . Always a learning experience.

[Brilstern]

Unfortunately the same outcome. But, mainly because I have no personal attachment to SendObject I am moving to a late binding function and going to try that, still making some adjustments to some code that I dug up from a past project.

One thing to note:

When I open my application without allowing my AutoExec macro to run and hide my Access Window, remove shortcuts, etc. (holding shift) I can actually run the email function and cancel it just fine and the error is trapped. If I let the app run as normal (which locks down all user control to only what I have allowed) it gives the error which freezes the application. Not really sure why though...

[ADezii]

As a side note, if Outlook is your Default E-Mail Client, you can gain much greater flexibility using it to E-Mail the Report with either Early or Late Binding.

[Brilstern]

I am using outlook, hence the late binding. But I am developing this for versatility so I prefer to stay away from early binding.