Decide on a number of columns and stick with it. Either that or make
separate forms/reports for each number of columns.
Then make your crosstab columns based on a "relative date" for instance
ColHead: "D" & DateDiff("d",[SaleDate], Date())
Set the Column Headings property to something like:
D0, D1, D2, D3,...D10
The D0 column will display today's values.

Signature
Duane Hookom
MS Access MVP
> Hi,
>
[quoted text clipped - 13 lines]
>
> ciao
Craig Hornish - 24 Mar 2005 22:18 GMT
If John's data can fit on one page with 12 colums then I would say yes -
make one report with 12 colums and hide the others as needed.
But if you have to make multible reports, then you still can use the
same report. In a crosstab report I have done I take the column of were the
data starts (not counting the grouping for rows) and use that info to
populate the colunms on the report about 8 that are not row information then
for the next grouping I have a modifier that adds to this to tell where I
should start the next set of data.
I just have a form that gathers this information. No need to have
multiple reports.
If you have the Solutions database it has a good example of how to limit
the number of shown columns.
Craig Hornish
temp@cap-associates.com - so I can delete it when it becomes a spam magnet
"Think outside the box, because anything is possible."
"How long it will take or whether it requires divine intervention is another
issue"
> Decide on a number of columns and stick with it. Either that or make
> separate forms/reports for each number of columns.
[quoted text clipped - 22 lines]
>>
>> ciao
Duane Hookom - 25 Mar 2005 03:38 GMT
The "Solutions.mdb" solution is horrible. There is a much better and
flexible solution for dynamic (any number of columns) crosstab reports at
http://www.invisibleinc.com/divFiles.cfm?divDivID=4. If John thinks he
really needs the flexibility of any number of columns (rarely necessary)
than I would recommend this solution. It allows any number of derived
columns from 2 to 100s. It is also much faster and requires less code than
the Solutions.mdb.

Signature
Duane Hookom
MS Access MVP
> If John's data can fit on one page with 12 colums then I would say
> yes - make one report with 12 colums and hide the others as needed.
[quoted text clipped - 43 lines]
>>>
>>> ciao