>> need more time.


Yes, that is true <s>. Please read the docs items to which I pointed you, for a start. Reading some of the other messages here, I am not even sure that you were aware of the FRX data session. Obviously you can read the structure of the FRX during the report. Everybody needs this, but everybody needs it for different reasons, so we just provide the whole thing "raw" in a place you can easily read it.

In general, the arguments of the various ReportListener events, and the ReportListener properties tell you what you *can't* learn from the FRX (items that are calculated and generated at runtime, such as position on the page or the value of an expression in the report, during a single report processing run). Meanwhile, the FRX tells you what you need to know about the design/layout information, and additionally (via memberdata or whatever devices you choose in User etc) can hold code you can use to further/dynamically adjust the report further at runtime.

>L<