I'm not sure either, but what steered me in the right direction was the use of the FIELD() API, in conjunction with tests for columncount FCOUNT(). Granted this is not perfect, as I can only put upwards of 10 columns in the report, but the user in theory could setup hundreds of columns (very unlikely).

>I'm not quite following...what does each page have to do with how many columns there are? Or is this just a way to test the reporting mechanism?
>
>As posed in the original question, it sounded like the entire report would have a certain fixed (but unknown at design time) set of data.
>
>>Thanks Tamar, not sure why I didn't think of that technique. Now I just have to figure out why the object rotation isn't working...
>>
>>>
>>>IOW, the first time through the loop, you report on data columns 1 through nColumns. The second time, it's nColumns + 2 up to 2*nColumns, etc.
>>>
>>>The expression for the data checks whether there's a field to report on in this column and if so, shows the data.
>>>