>>You need that when user decides which columns are list in report when reporting time...


Not necessarily. CREATE REPORT... FROM... has a FIELDS clause.

There are a number of ways to do this, though. Depends on how you want to set up the programmatically-designed report.

CREATE REPORT ... FROM is a good start but if it doesn't do what you want, and if a FIELDS list doesn't answer your issue, you can always set up a complete template report that's fancier. You then present the user with a fields list or other options and then *remove* the objects you don't want (or fill out their expressions and captions) before running the report.

As another alternative, consider including your template Frx in the PJX, and then copying it out in runtime. allow them to MODI REPO the temp copy. Now they can remove the columns they don't want or move stuff around.

>L<