>> define a report variable
>> and initialize it before printing (USE the FRX and REPLACE it's value)
>> works for me :)
>>
>> Arnon
>
>I use another trick:
>- in "group by" I put "eval(gr1)", "eval(gr2)", "eval(gr3)"
>- in group headers/footers, there's "tx1+' '+eval(gr1)" etc.
>
>In the routine calling the report, I just set these three pairs of vars
>(gr1 contains the field name, tx1 its description), according to the
>user's choice of ordering. This way, by recombining the orderings, I get
>six reports (or more, if gr1..gr3 may be chosen from a list with more
>than three rows) with one .frx (twelve, if we consider summary or not),
>and yet add some filtering to it (ID range, date range and such) and it
>eliminates the need for lots of other reports. Yes, the report is bound
>to the routine, but the routine does work like a swiss army knife.

Dragan -

Can I ask how you allow the users to choose the ordering and filtering (e.g. do you have a fixed list or do you base the contents of the list on some kind of a table)? It seems to me that while you have only 1 report form (good!), unless there is some way of generically getting this kind of info to the report form, you still have to create a number of custom print forms for each situation. Can you give an example?

Thanks,

Sylvia

BTW - I know this request is long after the original thread, but this info is new to me)...