Fix Microsoft Access PDF/A Export Fails Due to Tab Characters
Question details
Users are unable to export Microsoft Access 365 reports to PDF/A format when the report's text fields or labels contain tab characters.

- Product
- Microsoft Access 365
- Device & OS
- Windows 10
- Scenario
- Exporting an Access report to PDF/A format manually or via VBA (DoCmd.OutputTo) when the layout contains tab characters.
- Observed behavior
- The PDF/A export process fails entirely when a single tab character is present in the report, whereas standard PDF exports succeed without issue.
Ensure you have a backup of your Access database before modifying report layouts or running bulk update queries to remove formatting characters.
Remove or Replace Tab Characters in Report Data
Use this recommended method to sanitize your data or labels by replacing unsupported tab characters with spaces, allowing the PDF/A export to succeed.
The PDF/A standard has stricter encoding requirements than standard PDFs. Microsoft Access currently has a bug where encountering a tab character (Chr(9)) during PDF/A generation causes the entire export process to crash. Removing these characters resolves the issue instantly.
Open your Access database and review the tables or report queries supplying data to the failing report. Look for long text fields where users might have pressed 'Tab' for indentation.
Open your report's underlying query in Design View. Modify the text field by wrapping it in a Replace function: CleanField: Replace([YourFieldName], Chr(9), " "). This swaps tabs for spaces.
Open your report in Design View. Inspect any static Label controls for tab spacing. Delete the blank tab spaces and replace them with standard spacebar spaces.
Run your VBA export script or navigate to External Data > PDF or XPS, ensure 'PDF/A compliant' is checked in the options, and publish the report.

Redesign Report Layout Using Alignment Controls
Use this solution if you were relying on tab characters to align columns or text within a single label.
Export as Standard PDF
Use this workaround if PDF/A compliance is not strictly mandated by your organization or archiving system.
Try WPS Office for Seamless Document and PDF Management
While Microsoft Access handles complex databases, you might need a reliable, lightweight suite for your everyday documents, spreadsheets, and PDF exports. WPS Office offers excellent Microsoft Office format compatibility and robust built-in PDF features without heavy subscription costs or frustrating export bugs.
- 1. Download and Install: Visit the official WPS website to download the free, lightweight installer and complete the setup in minutes.
- 2. Open Your Office Documents: Launch WPS Office and open your existing Word, Excel, or PowerPoint files with perfect formatting preservation.
- 3. Export to PDF Reliably: Go to Menu > Export to PDF to effortlessly generate standard PDF or PDF/A files without character-related crashes.

Frequently Asked Questions
Why do tab characters break PDF/A exports in MS Access?
PDF/A is a standardized version of PDF designed for long-term archiving, requiring strict font embedding and character mapping. The Microsoft Access export engine currently has a bug where it fails to properly map the tab character (Chr(9)) to the PDF/A format, causing the entire export to abort.
Will changing file permissions fix the Access PDF/A export failure?
No. While file permission issues or storage quotas can sometimes cause export failures, this specific bug is triggered purely by report content. If a standard PDF exports successfully to the same folder but PDF/A fails, the issue is layout or data related (such as tab characters), not permission-based.
Is there a patch available for this Access 365 PDF/A issue?
As of recent testing on Access 365 (including version 2406, 64-bit), this reproducible bug still exists. Users are encouraged to report it directly to Microsoft via the 'Feedback' hub in Access. In the meantime, sanitizing the data to remove tab characters is the most reliable fix.




