ACC2: GP Fault Using Number As Group Header Name (124713)

SYMPTOMS

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.

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.

Start Microsoft Access and open any database.
Create a new report based on any table.
From the View menu, choose Sorting And Grouping.
In the first Field/Expression row, type =1. Set the group's GroupHeader property to Yes.
Add a control (such as a field or label) to the group header section.
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:

122927 WX1124: Microsoft Access Version 2.0 Service Pack