🚀 Overview

In Microsoft Access environments, IT administrators and database developers may encounter a specific runtime exception where the application triggers a “No current record” error message. This issue is primarily observed when a user attempts to generate a report via the Print or Print Preview commands. The error typically manifests while the user is actively navigating between different pages of the report. This behavior affects various Access file formats, including standard databases (.mdb and .accdb) as well as Microsoft Office Access projects (.adp).

⚙️ Key Technical Details

This specific error is the result of a known conflict within the Access reporting engine’s calculation logic. According to technical investigations, the “No current record” exception is triggered when the following four architectural conditions are met simultaneously within a report’s design:

• Multi-Field Grouping: The report is configured to group data based on multiple fields.
• Specific Group Properties: Within the grouping levels, the Group On property is explicitly set to Each Value.
• Active Group Footers: The Group Footer property for the affected group is set to Yes.
• Footer Expressions: The group footer contains functional calculations or summary expressions (e.g., Sum, Count, or custom formulas).

🛠️ Recommended Workarounds

To resolve this conflict and restore report functionality, administrators should implement one of the following structural changes to the report design. Microsoft recommends testing these methods sequentially to identify the specific trigger:

• Modify Grouping Logic: Navigate to the group properties and change the Group On setting from Each Value to Interval for one of the field groups.
• Disable Footer Sections: If the footer is not strictly necessary for the report’s layout, change the Group Footer property to No for one of the grouping levels.
• Remove Computational Logic: Strip any calculations or expressions located within the group footer section.

⚠️ Impact

This issue directly impacts productivity for end-users who rely on complex data summarization and physical documentation. Because the error often appears only during page navigation, it can lead to frustration and “half-printed” reports where the first page generates correctly, but subsequent pages fail. For IT administrators, this requires a design-level intervention rather than a simple software update, as Microsoft has confirmed this behavior is inherent to the product versions listed. It is vital to ensure that legacy .mdb or .adp files being migrated to newer environments are checked for these specific grouping configurations to prevent regression.

🔗 Official Source

Read the full article on Microsoft.com