AshikHusein
Registered User.
- Local time
- Today, 12:39
- Joined
- Feb 7, 2003
- Messages
- 147
I have created a reprt based on a crosstab query where the query totals the values within a certain field. So effectively that field becomes the column heading. The problem is that if there is one field missing ina table that I am analyzing, the report gives me an error saying that the field is not found. I can try to explain below:
Say that you have a field called "Callergroup" as the row heading and "Calltype" as the column heading.(it sums over a field called "TOTAL") Let us say assume that "Calltype" has three types of entries X,Y and Z.
Now when create the report from the crosstab query, X,Y, and Z will become the column headings. So assume that these will be the column headings for which I have designed and formatted the report for to be viewed by the management.
Now there are times that there may not be an entry, say Z, in the field "Calltype". Under these circumstances when I try to get the report it gives me an error saying that the field "Z" does not exist (since Z is one of the fields in the report previously created).
Is there a way to get around this so that even though the field does not exist the report assume that all TOTALS for that field will be zero but it does open the report without giving me an error. Thanks.
Say that you have a field called "Callergroup" as the row heading and "Calltype" as the column heading.(it sums over a field called "TOTAL") Let us say assume that "Calltype" has three types of entries X,Y and Z.
Now when create the report from the crosstab query, X,Y, and Z will become the column headings. So assume that these will be the column headings for which I have designed and formatted the report for to be viewed by the management.
Now there are times that there may not be an entry, say Z, in the field "Calltype". Under these circumstances when I try to get the report it gives me an error saying that the field "Z" does not exist (since Z is one of the fields in the report previously created).
Is there a way to get around this so that even though the field does not exist the report assume that all TOTALS for that field will be zero but it does open the report without giving me an error. Thanks.