Crosstab query with forced columns ?

[Rebecca]

If I have a crosstab query that forces the number of
columns regardless of whether data is found in those
columns, will that cause a problem in reporting?
In other words, when the report comes across a row and
column that has no data will it choke?
The source for my controls is set to 1 thru 8 representing
the crosstab columns. Do I have to test for nulls?

 

[[MVP] S. Clark]

As long as the Field exists, the report will be fine.


--
HTH,

Steve Clark, Access MVP
FMS, Inc.
Professional Solutions Group
http://www.FMSInc.com
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Is your Access database too slow?
Are you ready to upgrade to SQL Server?
Contact us for optimization and/or upsizing!
http://www.FMSInc.com/consulting
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

[Rebecca]

How do I make the fields 'exist'.
The Jet Database engine is not recognizing them.
They are created by a crosstab query with a PIVOT from
column values in another query.

 

[Sal]

Try to use an IIF statement to calculate your crostab
fields instead, with subqueries.
It is the only way

Sal

 

[Duane Hookom]

Enter all the possible column heading values into the Column Headings
property of the query.

 

[Zeppo]

Enter all the possible column heading values into the Column Headings
property of the query.

Don't you Access MVP's ever relax? :~)

www.rac4sql.net

 

[Duane Hookom]

This is relaxing...

 

[[MVP] S. Clark]

Yes, but I do it at 130MPH. Check it out: www.tightsqueezeracing.org

 

[Duane Hookom]

On two wheels (at least)?