Your idea should work and you are right .. the only thing that identifies the band is the VPOS of the item. You also have to make sure that you account for the height of the gray bar that defines each band. The FRX assumes this height is included in each object!

Cathy


>After a quick look into the structure of a frx
>I believe I will do fixes with smaller group bands,
>which should get me through first deployment
>and offer programmtic changes of the frx if there are
>many calls of changed layout.
>
>I guess on 95% it will work out, and then it depends
>on the status of the insurance broker who finds a different
>layout.
>
>If you don't mind, please check my idea:
>
>First wrap every report call into a function, and create a temporary .frx to modify and print. Since everything is in arrays, I should be able to walk
>the temp.frx evaluating the supexpr to find the supressed items.
>If the frx is ordered beforehand on the vPos, it should be possible to identify totally supressed lines, add their height, find the band they are in (no linkage found: I guess this is done using the VPos and the cumulated height of the bands, which were nicely ordered in the few frx I checked) and fix it's height:
>with a little bit of work this could be made generic for all
>the reports in the system. Anything totally wrong in my thinking ?
>
>Just to be sure I don't promise something I can't deliver ?
>
>tia
>
>Thomas