Thanks Farhad but no I do not think that would work becuase there are multiple bills to print, each of which must have its own summary. And the detail lines could run 1, 2, 3 or more pages and then a summary comes for that bill and then the next bill prints.

The billheader has a primarykey and each of the child files has an index on the foreign billheader key. And a relation and set skip to was set on both the child files when I tested the two detail bands. Right now I have a one-to-many relationship betwen the billheader and billine tables and a one-to-one relation between the biilheader and billsummary files.


>Dear Bruce,
>
>Realy I'm not sure that my idea can be helpful or no because I don't know about the table structure and their relations which are important when we make decision to define detail bands and groups.
>
>If it was possible to put the summary in summary band at the end of report page you could force it to be printed in a seperate page.