DoCmd SendObject The SendObject action was cancelled. You can't exit Microsoft Access now.

[RyanP]

DoCmd.SendObject acSendReport, stDocName, acFormatPDF, "", , , "Emailing" & " " & strFileName


'Close the Report
DoCmd.Close acReport, stDocName

Exit_cmdX_Single_Click:
Exit Sub

Cancel_cmdX_Single_Click:
Exit Sub


Cancel = True

Err_cmdX_Single_Click:
DoCmd.Close acReport, stDocName

Exit Sub
Cancel = True
DoCmd.CancelEvent
MsgBox Err.Description
Select Case Err.Number
Case 2501

This triggers but I still get the "The SendObject action was cancelled" message and subsequent application FAIL

End Select
Resume Exit_cmdX_Click
End Sub


Scenario:
1) User closes the email without sending.
2) They get the "The SendObject action was cancelled" message
3) Then the Access application is locked and cannot be closed "You can't exit Microsoft Access now. If you're running a Visual Basic module that is using OLD or DDE, you may need to interrupt the module.
4) User is forced to shut down MSACCESS.exe via Task Manager


The cancel event was added as an attempt to stop this from happening all to no avail. Tried various methods; turning off the error description, exiting the sub etc... None trigger in the ACCDE.

In the ACCDE, if they use the X button to close the message without sending the email, the "The SendObject action was cancelled" message appears and insert FAIL function

Windows 7 32 & 64 bit : Office Pro Plus 2010 32 bit (mix of 14.0.6029 & 14.0.7015) (tested on multiple PCs, all behaving the same way): ACCDE database

This was marked as solved on the "sendobject on cancel error" however I'm not entirely sure why or how...

[ranman256]

I dont see the need for ALL this code.
Remove everything except:

DoCmd.SendObject acSendReport, stDocName, acFormatPDF, "", , , "Emailing" & " " & strFileName
end Sub

And you get an error put back the error handling part:

Exit Sub

errSend:
MsgBox Err.Description

[ItsMe]

Are you trying to trap an error 2501?

You need to put your error trapping prior to your first Exit Sub line. Do you have an on error GoTo Err_cmdX_Single_Click prioir to your DoCmd.SendObject?

[RyanP]

Are you trying to trap an error 2501?

You need to put your error trapping prior to your first Exit Sub line. Do you have an on error GoTo Err_cmdX_Single_Click prioir to your DoCmd.SendObject?

Yes, I have that... just didn't include it in the code example (sorry)

It goes to the error properly, but does not proceed to the EXIT... Access gets locked and cannot be closed "You can't exit Microsoft Access now. If you're running a Visual Basic module that is using OLD or DDE, you may need to interrupt the module.

[RyanP]

I dont see the need for ALL this code.
Remove everything except:

DoCmd.SendObject acSendReport, stDocName, acFormatPDF, "", , , "Emailing" & " " & strFileName
end Sub

And you get an error put back the error handling part:

Exit Sub

errSend:
MsgBox Err.Description

If I have no On Error GoTo / Error code, then ACCDE just outright fails. If I have the On Error GoTo / Error code (resume Exit) the ACCDE goes to the error properly, but does not proceed to the EXIT... Access gets locked and cannot be closed "You can't exit Microsoft Access now. If you're running a Visual Basic module that is using OLD or DDE, you may need to interrupt the module.

As for the cancels etc... I didn't have them there initially. They were an in vain attempt to avoid the "The SendObject action was cancelled" / "You can't exit Microsoft Access now. If you're running a Visual Basic module that is using OLD or DDE, you may need to interrupt the module." scenario...

[RyanP]

Doesn't look like I noted it on my initial post. If I'm in a ACCDB, this does not occur. Only an issue in the ACCDE...

[ItsMe]

Doesn't look like I noted it on my initial post. If I'm in a ACCDB, this does not occur. Only an issue in the ACCDE...

I should have a chance to check this out later. I will try and create an error trap to manage it. It might be as easy as adding a Do Events.

[ItsMe]

I was able to get this to work in an accdr. No error or message box or anything.

Private Sub Command0_Click()

On Error GoTo MyError

DoCmd.SendObject acSendReport, "ReportName", acFormatPDF, "Me@Domain.com"

Resume_MyError:
Exit Sub

MyError:
Select Case Err.Number
Case 2501
GoTo Resume_MyError
Case Else
MsgBox "There was an error." & vbCrLf & Err.Number & vbCrLf & Err.Description
GoTo Resume_MyError
End Select

End Sub

[RyanP]

In the ACCDE with the Nav Pane displayed, I do not get the error using your code.
I didn't realize it had any bearing on the subject so I didn't mention it before; but it appears that the problem is only present in the ACCDE when I set the Current Database - Display Navigation Pane setting to OFF.
In that scenario, the error appears with your code as well.

Doesn't matter if the NAV Pane is turned off via the Current Database Option or programmatically via VBA.

Aside from a workaround, why would the NAV PANE being hidden have such an effect?

[ItsMe]

...Display Navigation Pane setting to OFF.
In that scenario, the error appears with your code as well. ...

I just tested the code I posted with the Nav Pane hidden via the options. I went through the extra step of making an accde vs. changing the extension to accdr. I did not have any issues launching a new Email, canceling, and then launching another email. I tried the same thing with the Nave Pane visible, no issues.

Not sure why you are still having problems. I have used similar code in production DB's as executables and never had a problem. Perhaps you can do like I did and make a separate, blank, DB. Drag a table into it and run the Wizard to create a Report. Then test the code in the new DB.

[RyanP]

new blank DB with 1 form to call, one report to export and 1 table as the recordsource... accde / accdr dont' get the "The SendObject action was cancelled" / "You can't exit Microsoft Access now. If you're running a Visual Basic module that is using OLD or DDE, you may need to interrupt the module." scenario...


Made a new DB. imported all objects, set the appropriate VB references. make the accde and accdr. "The SendObject action was cancelled" conflict in the Library references?

[ItsMe]

using OLD or DDE

I am not sure what OLD is. I don't suppose your are using DDE if you created a new DB. Perhaps there is a default setting in options for DDE that is global. I did not create any special references in my sample DB. My DB file is in a trusted Folder. That is the only thing I can think that might be different.

I do not get the same error message you get if I comment out the Error trapping.

.

[RyanP]

sry...OLE. my bad

noticed someone else had this problem at some point....Error Handling if DoCmd.SendObject is cancelled

am fine with giving up on DoCmd.SendObject based on everything i've read on it.
But alas, still a newb and not 100% how to convert the report to pdf and attach it to the email without using DoCmd.SendObject OR not having to save the PDF to a file first.
Not a bid deal though. I guess I can just use the OutputTo acReport to a predefined location and use it as the attachment

[ItsMe]

I will work up some examples after I get some sleep.

[ItsMe]

This code seems to work good as a standalone. I did not have any issues with warnings, security or otherwise.

'before exporting your report you will want to make
'sure there is not a file in the folder with the same name
'and that the folder actually exists

'create a report in a temp folder
DoCmd.OutputTo acOutputReport, "ReportName", acFormatPDF, "C:\Test\PDF_Files\Test.pdf"

'Reference Microsoft Outlook and
'use early binding
Dim objOutlook As New Outlook.Application
Dim objNewEmail As MailItem
Dim objAttachReport As Attachments

'Instantiate your objects
Set objNewEmail = objOutlook.CreateItem(olMailItem)
Set objAttachReport = objNewEmail.Attachments

'Add your file to the Attachments Collection
objAttachReport.Add "C:\Test\PDF_Files\Test.pdf", olByValue

    With objNewEmail
        .BodyFormat = olFormatRichText
        .To = "MyEmail@Domain.com"
        .Subject = "Test Message"
        .HTMLBody = "This is the body of the message"
        'Save the email to ensure the attachment is a
        'copy of the original file (olByValue)
        .Save
        .Send
    End With

'tidy up
Set objAttachReport = Nothing
Set objNewEmail = Nothing
Set objOutlook = Nothing

MsgBox "Complete"