A warning about insufficient memory or disk space can send someone straight to deleting files or changing a database. For some Microsoft Access users, that diagnosis may be wrong. The safer response is to preserve the source, identify the exact Office build and separate a software issue from a genuine storage problem before making changes.
What Microsoft documented
On 23 October 2026, Microsoft published its Access Version 2610 update notes. The post lists a known issue in the initial Version 2610 release: some databases may show an incorrect “There isn't enough memory or disk space” message when a report is opened or exported to PDF. Microsoft says a correction is planned for the next Version 2610 update.
That wording matters. Microsoft does not say that every similar message is false, that every Access database is affected or that the cited build already fixes this particular problem. The post also does not provide a universal workaround. A real full drive, unavailable network folder or permission problem can still stop an export.
A careful response checklist
1. Capture the exact failure. Record the message, report name, database filename, export destination and time. In Access, note the full version and build from the account information page. If another person reports the problem, ask for those facts rather than relying on “PDF is broken.”
2. Check the basics without deleting anything. Confirm that the destination exists, is reachable and has reasonable free space. Check whether the user can create an ordinary test file there. If the storage is genuinely full or access is denied, follow the organisation's IT process. Do not compact, repair or restructure the only database merely because this message appeared.
3. Preserve the database. Keep the current source and a known-good backup under the organisation's normal access controls. Test on an approved copy where possible. Repeated experiments on the live database make it harder to distinguish the original fault from later changes.
4. Narrow the test. Determine whether the same report opens, whether another report exports and whether the failure appears only in Version 2610. Avoid using confidential production data in an unapproved service. The purpose is to describe the affected path, not to prove a speculative cause.
5. Coordinate the update. Ask the Microsoft 365 administrator to monitor Microsoft's official Access notes for the promised Version 2610 correction. When it arrives, apply it through the organisation's normal update policy, then repeat the same controlled export and record the result. Do not assume an unrelated Windows or Office update contains the fix.
6. Plan an authorised deadline route. If the PDF is urgent, ask IT whether an approved unaffected build or workstation is available. If a different reporting route is authorised, compare its totals, filters, page layout and timestamps with the Access report. Do not upload the database itself to a generic converter.
Check any PDF that is produced
A successful export still deserves inspection. Confirm the report title, filter period, page count, group headers, totals, footers and content near page edges. Open the exact file that will be sent, not only the on-screen Access preview.
FileStation cannot open or repair Access databases and cannot resolve this Version 2610 issue. After an approved system has produced the PDF, PDF Reader can support a visual page check, while the CLEAR document check offers a simple final-review routine. Keep the Access source and approved backup separate.
The practical lesson is simple: an error message is evidence of a failed step, not always a reliable diagnosis. Preserve first, verify the environment and wait for Microsoft's documented correction rather than making destructive guesses.
Primary source: Microsoft Access Blog, “Fixes in Microsoft Access - Version 2610 (Build 16.0.20527.20088),” 23 October 2026.