>> .... I believe there's some documentation that came with VFP describing the structure.
>

>repo form HOME(1)+'Tools\Filespec\90frx.frx' preview
>

>Beware! The order of records is important!
>
>The hight of summary might be as complex as any other section of the report. Simple ones without dynamic height changing and self hiding stuff you might gather from frx.
>If you need to deal with dynamics, try to dive into report listener - it might be the best place to get the height of a report section.
>Anyway, I do not use report summary band at all - I wrap the whole report in a group like .F. and use the summary of this group. Gives better control.

One thing that could be annoying is that the report header and footer bands are separate from the reset of the "body" and the page header and footer aren't applied. Adding a group that encompasses the entire report and placing using the group header and footer allows you to use the normal page header and footer for these bands.

Where this sort of becomes important is when I set up the report form so that spans the entire page rather than the printable area. The problem of selecting "printable area" for the extents is that the positioning of the content ends up varying from printer to printer (since the margins that define the printable area may not always be symmetric nor consistent across different printer models). I usually set the report to use entire page and set aside the margins (I usually leave around 3/8" to 1/2" of the edge of the page blank).