'No Current Record' Error when Outputting Report to PDF from Batch File or Task Scheduler

Question

The Problem

I'm using a scheduled task to open an MS Access database, run a macro to email a report in PDF format, and then close the database. The report is relatively basic and the macro simply uses the EmailDatabaseObject action to export & email the report in PDF format.

This has been running successfully on a daily basis for the past 4 years on a Windows 7 machine running the latest version of Office 365 compatible with Windows 7.

I've recently updated the machine to Windows 10 and I'm now encountering a No Current Record error when running the scheduled task. After clicking OK to the error several times, Windows reports that MS Access has stopped working and the application crashes.

If I manually open the database and manually run the macro, everything is successful.

Setup

• Windows 10 Pro 20H2 (19042.964) 64-bit
• Office 365 Apps for Business 2104 (13929.20296) 32-bit

My Research

• I've found this MS KB article describing the issue, however, this reportedly applies to MS Access 2003 & 2007. My report has no grouping, but does contain summations in the report footer. However the suggested solution is not feasible since removing the summations would remove necessary information from the report.

• I've found this related question, however, this attributes the cause to accessing the database from OneDrive as opposed to a mapped network drive, whereas I am accessing the database from a mapped network drive.

• This looks to be the same issue, but I cannot access the 'solution' at Experts Exchange...

What I've Already Tried

• Rolling back Office 365 to an earlier version (version 2101).

• Running the Scheduled Task with Highest Privileges - but this results in no access to mapped network drives.

• Running the macro from a batch file.

• Opening the database from another PC and running the macro from a batch file.

• Perform the operations using the AutoExec macro rather than invoking a specific macro by name.

• Imported all objects from the database into a new local database.

• Exporting the report as a PDF locally using the ExportWithFormatting action.

• Using the DoCmd.SendObject method to email the report - this results in MS Access immediately crashing.

• Changing the default Windows printer & default report printer to 'Microsoft Print to PDF' to rule out possible printer driver issues.

Current Workaround

I've found that this error only arises when the export format is set to PDF; as such, my current workaround is to export the report to RTF format - but this is obviously not ideal.

---

Update

I've now systematically removed items from the report until I was able to run the report successfully from the scheduled task.

I removed items until I was left with a single static label in the Report Header and a set of fields in the Report Detail referencing basic numeric & text data from a single table in the database.

Removing the Report Header & Footer resulted in the report running successfully from the scheduled task, and so I determined that the issue must be caused by a setting associated with the Report Header/Footer.

I isolated the issue to the 'Force New Page' setting in the Report Header:

With this set to 'After Section', the report crashes; but if this is set to 'None', the report is successful.

However, when setting this to 'None' in the original report, the report still crashes when run from the Task Scheduler and output to PDF.

Steps to Reproduce the Problem

I've uploaded an incredibly basic database here, containing a single table, a single report, and a single macro which executes the ExportWithFormatting action followed by the QuitAccess action.

To reproduce the problem, open a command prompt window and issue the following commands:

cd C:\Program Files (x86)\Microsoft Office\root\Office16
msaccess.exe C:\YourPath\test.accdb /x macro1

MS Access should then open and you may be presented with the 'No Current Record' error.

---

Has anyone else encountered this issue and knows of a solution?

Many thanks for your time.