>>
Try using field(ix) as Fieldname and eval(field(ix)) as Value in report. >This would let you have a generic report and yet prevent overflows (crosstab >might generate say 250 columns but you'd always show first n columns).
>>Cetin
>
>Thank you for the suggestion. I'll bet I didn't do what you meant.
>I put a field on the report, and in the Expression box typed field(ix)
>I get error, variable ix not found. I put it in quotes, I get text.
>
>Does (ix) stand for something I missed?
>
>
>Thanks again.
>-Sylvia
ix stands for field order. If your crosstab returns fields like myRowData, Col1, Col2, Col3 you would use field(2) where you want to appear "Col2" and eval(field(2)) where you want the value of Col2 (detail line) appear (Instead of hardcoding "Col2" as Label and Col2 as field expression). Both field(2) and eval(field(2)) are field expressions in report (add Field controls to page header and detail and set expressions as field(2) for label and eval(field(2)) as detail line).
Cetin
