ACC1x: "...Isn't a Valid Parameter Name" Err Msg Running Report

Last reviewed: May 14, 1997
Article ID: Q120129
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SYMPTOMS

When you print or preview a report, you receive the error message:

   '[<tablename>.<fieldname>]' isn't a valid parameter name

CAUSE

You used the Groups/Totals Report Wizard to create the report, and either the report's record source is a multiple-table query containing identical field names (for example, Orders1.Order Amount and Orders2.Order Amount), or you are summing two fields with identical names in your report [for example, =Sum(Orders1.Order Amount) and =Sum(Orders2.Order Amount)].

RESOLUTION

Use aliases in the underlying query to avoid duplicate field names. For example, use the following expressions to create aliases called Expr1 and Expr2:

   Expr1: [Orders1].[Order Amount]

   Expr2: [Orders2].[Order Amount]

You can then refer to these aliases in your report. The following examples demonstrates how to sum the aliases:

   =Sum([Expr1])

   =Sum([Expr2])

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access versions 1.0 and 1.1. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

REFERENCES

Microsoft Access "User's Guide," version 1.0, Chapter 17, "Report Basics," pages 400-401

Microsoft Access "User's Guide," version 1.1, Chapter 17, "Report Basics," pages 404-405


Additional query words: reportwizard param
Keywords : kberrmsg kbusage RptWizg
Version : 1.0 1.1
Platform : WINDOWS
Hardware : X86
Issue type : kbbug
Resolution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.