Others

How to Fix an Access Report Showing #Error After a Parameter Entry

Bushra ParveenBushra Parveen Nov 2, 2026 868 views

Question details

Users need to resolve an issue where a Microsoft Access report displays #Error instead of the expected data or zero after entering a parameter.

How to Fix an Access Report Showing #Error After a Parameter Entry
Product
Microsoft Access
Device & OS
not provided
Scenario
Generating a report that uses a calculated text box containing a parameter or aggregate expression, particularly when the underlying query returns no records.
Observed behavior
The calculated text box on the report shows #Error instead of properly returning the calculated value or defaulting to zero.
Before you start

Before attempting to modify your report expressions, ensure you have a backup of your Access database and verify that the exact parameter names used in your queries match your intended inputs.

Solution 1Recommended

Reference a Control on an Open Form

This is the most reliable workaround. By linking the report to a form instead of relying directly on a parameter prompt, you can prevent evaluation errors when no records are returned.

When an Access report opens without underlying data, calculated text boxes that rely on parameter prompts can fail to evaluate, resulting in an #Error message. Referencing an active form bypasses this limitation.

1
Create a parameter form

Create a new blank form in Access and add an unbound text box for the user to enter the parameter. Name the form (e.g., 'frmParameters') and the text box (e.g., 'txtStartDate').

2
Keep the form open

Add a button to this form that opens your report. Ensure the form remains open in the background (you can make it hidden if preferred) while the report is generated.

3
Update the calculated text box

Open your report in Design View. Select the calculated text box that is displaying the error, go to the Property Sheet, and change its Control Source to reference the form using the syntax: =Forms![frmParameters]![txtStartDate]

Reference a Control on an Open Form
Data Persistence: Using a form to capture parameters also allows you to easily reference the same input across multiple queries or reports without prompting the user multiple times.
Free Microsoft Office alternative

Looking for a Lightweight Alternative to Microsoft Office?

While Microsoft Access handles complex relational databases, a significant portion of daily data analysis, reporting, and parameter-based querying can be performed effortlessly using WPS Spreadsheet. WPS Office offers a free, lightweight suite that is fully compatible with major document formats.

  1. 1. Download the installer: Visit the official WPS Office website and download the free installer package for your operating system.
  2. 2. Install the suite: Run the setup file and follow the on-screen instructions to complete the fast installation process.
  3. 3. Open WPS Spreadsheet: Launch WPS Office and open WPS Spreadsheet to easily manage your data, utilize advanced formulas, and create dynamic pivot table reports.
Highly compatible with Microsoft Office formats (.docx, .xlsx, .pptx)Easily analyze structured data and generate robust reports as an alternative to complex database softwareFree, lightweight, and fast to install on any deviceFamiliar user interface for immediate productivity and seamless migration
microsoft office alternative - wps office

Frequently Asked Questions

Why does my Access report show #Name? instead of #Error?

The #Name? error typically occurs when the Control Source contains a typo, references a field that does not exist in the report's underlying query, or lacks the '=' sign at the beginning of an expression.

Can I prevent a report from opening entirely if there are no records?

Yes. You can use the 'On No Data' event of the report. In the event procedure, type 'Cancel = True' and optionally add a MsgBox to inform the user that no records were found matching their parameters.

Does the Nz() function work in report queries or just on the report design?

The Nz() function works perfectly in both. It is often considered best practice to handle null values at the query level using Nz() so the report receives clean data before rendering the text boxes.