D
Dave Lampron
Hello,
I have been trying to debug a crosstab query that I wrote
in Access 97. The query does not display a value in the
Column Heading field. This problem always occurs on the
same records when the query is run. The query is counting
the total values without incident but not always
displaying the values in the Column Heading field.
However, the problem disappears when I run the query on
Access 2002. Is there a bug with the 97 Db engine?
For Example:
This is what the query does in Access 97:
RecNum Name Total Colw Colx Coly Colz
1 Bob 4 1 1 1 1
2 Jane 4 1
3 Bill 4 1 1 1 1
4 Sue 3 1 1 1
5 Mary 4 1
--Records for Jane and Mary are not displaying properly
This is what the query should do (and does in Access 2002):
RecNum Name Total Colw Colx Coly Colz
1 Bob 4 1 1 1 1
2 Jane 4 1 1 1 1
3 Bill 4 1 1 1 1
4 Sue 3 1 1 1
5 Mary 4 1 1 1 1
I have tried every method that I can think of to debug
this. The fact that the query works just fine in a newer
version of Access leads me to believe that there might be
some sort of bug in the Access 97 engine. Any advice would
be much appreciated.
thanks,
Dave
I have been trying to debug a crosstab query that I wrote
in Access 97. The query does not display a value in the
Column Heading field. This problem always occurs on the
same records when the query is run. The query is counting
the total values without incident but not always
displaying the values in the Column Heading field.
However, the problem disappears when I run the query on
Access 2002. Is there a bug with the 97 Db engine?
For Example:
This is what the query does in Access 97:
RecNum Name Total Colw Colx Coly Colz
1 Bob 4 1 1 1 1
2 Jane 4 1
3 Bill 4 1 1 1 1
4 Sue 3 1 1 1
5 Mary 4 1
--Records for Jane and Mary are not displaying properly
This is what the query should do (and does in Access 2002):
RecNum Name Total Colw Colx Coly Colz
1 Bob 4 1 1 1 1
2 Jane 4 1 1 1 1
3 Bill 4 1 1 1 1
4 Sue 3 1 1 1
5 Mary 4 1 1 1 1
I have tried every method that I can think of to debug
this. The fact that the query works just fine in a newer
version of Access leads me to believe that there might be
some sort of bug in the Access 97 engine. Any advice would
be much appreciated.
thanks,
Dave