It wasn't my efforts, David, and once again, thanks for the great example.

As far as how perfect this solution is: There is some arithmetic that will need to be done to waste as little space as possible and be as attractive as possible -- but this would have been true no matter how the change was implemented. I think you could see this in the sample.

From a catalog perspective, you will probably still want to set the band height parameters and the picture sizes with an eye towards making everything come out neatly, whether a catalog entry does or does not have a picture. You'll want to think carefully about the picture attributes (for example I would recommend their being exactly the same size, possibly centering in frame, etc), whether you want a band to be pushed down to the next page if there isn't enough room for all the text under the picture for a certain entry, etc.

Although you get a little more help from the report layout (because of multiple detail bands) in VFP 9 in this respect, your real leverage comes from being able to hook into the rendering process, using reportListener objects, to do this kind of math yourself instead of relying on the engine to make these decisions perfectly to fit every case.

Should be fun to watch <g>. Should also be a lot of report developers shooting themselves in the foot for a while, getting used to all the power at their disposal <g>.

>L<