ACC2: GP Fault Using Number As Group Header Name

Last reviewed: May 27, 1997
Article ID: Q124713
The information in this article applies to:
  • Microsoft Access version 2.0

SYMPTOMS

Novice: Requires knowledge of the user interface on single-user computers.

When you use a numeric expression (such as =1) as a group header name in a report, you receive one of the following error messages when you print or preview the report:

  • ORDER BY clause [<field name>] conflicts with GROUP BY clause

    -or-

  • MSACCESS caused GP Fault in MSAJT200.DLL

NOTE: Users creating dummy groups by including =1 in the Sorting and Grouping dialog box may encounter this problem.

CAUSE

This problem occurs only if you have installed the Microsoft Access version 2.0 Service Pack. The Microsoft Jet database engine version 2.5 that is included with the Service Pack introduces the ability to order data by ordinal numbers. When you try to use an ordinal number as the name of a group header in a report, the Microsoft Jet database engine erroneously attempts to interpret the ordinal number.

RESOLUTION

Put quotation marks around the number to make it a text string (for example, ="1").

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access version 2.0 using Jet 2.5. This problem no longer occurs in Microsoft Access version 7.0.

MORE INFORMATION

Steps to Reproduce Problem

WARNING: Following these steps may cause a general protection (GP) fault on your computer. Save and close any open work on your computer before following these steps.

NOTE: In order to reproduce this problem, you must have the Microsoft Access version 2.0 Service Pack installed.

  1. Start Microsoft Access and open any database.

  2. Create a new report based on any table.

  3. From the View menu, choose Sorting And Grouping.

  4. In the first Field/Expression row, type "=1" (without quotation marks). Set the group's GroupHeader property to Yes.

  5. Add a control (such as a field or label) to the group header section.

  6. Preview the report. You receive the error message:

          MSACCESS caused GP Fault in MSAJT200.DLL
    

    The error message

          ORDER BY Clause [<field name>] conflicts with GROUP BY clause.
    

    is generated if you have multiple group headers and the numeric group header is the outermost group.

REFERENCES

For more information about the Microsoft Access version 2.0 Service Pack, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q122927
   TITLE     : WX1124: Microsoft Access Version 2.0 Service Pack


Additional query words: gpf jet25 jet 2.5
Keywords : kberrmsg kbusage RptSort
Version : 2.0
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 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.