It is readwrite because it is completely for user-use.


It is how the engine gives us information, mostly about what the original REPORT FORM command looked like, but the engine never uses it -- just as the engine provides the copy of the FRX in the special data session for our use -- the engine pays no attention to the FRX after reading it into a structure we can't access, at the beginning of the report run).

However, unlike the copy of the FRX, you can use the CommmandClauses properties to pass information around, between multiple listeners or between events. Since the engine doesn't care about it, it's totally "there" for you.

Actually there is one time that the engine pays attention to a few of the CommandClauses values (this is all documented): when the Xbase Preview app passes command back to the engine when you choose to Print from Preview. And this makes sense; the engine at this point has no recourse except CommandClauses to find out what the original REPORT FORM command looked like, just like us <s>. So we have the opportunity to (for example) adjust the print range and tell the engine about it.

HTH,

>L<