>Hi everybody,
>
>That's a continuation of the thread I posted few days ago. I guess my manager bought the idea of converting that report into @SAY commands for better control. My qyestion is: how to ease that conversion? What class is available, what can help?
>
>I know there are two classes: one by Hilmar and another by Srjdan. I never tried any of them. What exactly they are doing and should I get one of them (which one) to get that job done as quickly as possible. So far we're talking about one particular not extremely complicated report.
>
>Thanks in advance.

I never tried Srjdan's class, but I understand that it supports several output formats.

My own reporting class:

Has methods for selecting data, printing detail band, page header, page footer, group header, group footer, report header, report footer.

You should use wrapper functions .Print() and .PrintLine() (equivalent of ? and ??), so that the class keeps track, properly, of line numbers, column numbers. Similar for pagebreak - you should use the corresponding wrapper function.

Supported output: Epson dot-matrix printers (you will likely need to adjust printer codes for other printers), preview either in default text editor, or default browser. Also supports Excel.

Supports multiple columns.

Is quite flexible; for example, you decide whether you want to start each record on a new line or not.

The sample included is quite self-explanatory, IMNSHO.

Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)