Fix Access Error 2294 When Sending Outlook Email with an Attachment
Question details
User needs a reliable way to send a Microsoft Access report as an Outlook email attachment after DoCmd.SendObject fails with error 2294 on some Windows profiles.
- Product
- Microsoft Access and Microsoft Outlook
- Device & OS
- Windows
- Scenario
- User runs DoCmd.SendObject from VBA or the External Data tab to email an Access report as a PDF, but sending fails only on certain Windows profiles or computers.
- Observed behavior
- Microsoft Access displays error 2294: "Access can't attach the object; the message was not sent." Removing the attachment lets the email send successfully.
Before changing VBA code, verify that the PDF export folder exists and that you can manually attach a file to an Outlook email on the affected profile. Also confirm Outlook and Access are running with the same architecture (32-bit or 64-bit).
Use Outlook automation to export the report and attach it
Recommended when DoCmd.SendObject returns error 2294 because it gives you direct control over file creation and the Outlook attachment.
DoCmd.SendObject relies on Simple MAPI and can fail based on the current Windows profile, Outlook security settings, or MAPI configuration. Outlook automation gives you direct control over creating the PDF and attaching it, which avoids the failing SendObject path.
In Microsoft Access, open the database and identify the report you want to email.
Use DoCmd.OutputTo acOutputReport, "ReportName", acFormatPDF, "C:\Temp\Report.pdf" to create the PDF file in a known folder.
In VBA, create an Outlook.Application object and use CreateItem(0) to create a new Outlook MailItem.
Call MailItem.Attachments.Add "C:\Temp\Report.pdf" to add the exported file to the message.
Set the recipient, subject, and body, then execute MailItem.Send to send the email.
Test a new Windows profile and verify Office updates, versions, and permissions
Use this when the error follows specific Windows profiles or installations rather than the VBA code itself.
Use WPS Office as a Lightweight Alternative for Report Attachments
Access error 2294 is a Microsoft Access/Outlook automation issue. WPS Office cannot patch Access, but it offers a free, lightweight Office alternative for creating, editing, and exporting Word, Excel, PowerPoint, and PDF files with familiar tools and strong Microsoft Office format compatibility.
Frequently Asked Questions
Why does DoCmd.SendObject return error 2294 only for Access but not Word or Excel?
DoCmd.SendObject uses the Access Simple MAPI path, which can be affected by the current Windows profile, Outlook security settings, and MAPI configuration. Word and Excel do not use the same Access DoCmd.SendObject call, so they may still attach files successfully.
How do I send an Access report as a PDF when DoCmd.SendObject fails?
Use Outlook automation: export the report with DoCmd.OutputTo to a known PDF path, create an Outlook MailItem, add the PDF with Attachments.Add, and call Send. This bypasses DoCmd.SendObject.
Will creating a new Windows profile fix Access error 2294?
It often helps if the original profile is corrupted. Create a test Windows profile from Settings > Accounts > Family & other users, then run the same send process. If it works, migrate the affected user to the new profile.
Do Microsoft Access and Outlook need to be the same Office bitness?
Yes. Mismatched 32-bit and 64-bit Office components can cause automation issues. Check File > Account in both apps and ensure they match.
Does WPS Office have an Access or Outlook automation error like 2294?
No. WPS Office does not include Microsoft Access or Outlook automation. You can use WPS Office to create and export PDF reports and then attach them through your normal email client.
