Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Grouping and Repeating Header

edited May 2004 in General
I have a report with a group header which has keep together and
reprint on subsequent pages. If I run into an (abnormal) situation
where the group header takes up a full page (or maybe even more),
the report keeps reprinting the header ad infinitum (a client watched
a pdf go to 1600+ pages). What are my options for "dealing" with
this issue? (I have D7E and RB7E.) Thanks.

Comments

  • edited May 2004
    Hi John,

    Be sure you have the Report.AutoStop property set to True. See the
    following article on troubleshooting endless pages. If you are still
    experiencing the issue, please send an example to
    support@digital-metaphors.com and I'll try to run it on my machine.

    ------------------------------------------------------
    Article: TroubleShooting: Report Prints Endless Pages
    ------------------------------------------------------

    Occasionally, we have customers state that their reports are in some
    infinite state where page after empty page prints forever.

    There are a few items to check when this occurs.

    The TppReport.AutoStop property is the first thing to check. If this is
    false when the DataPipeline property is unassigned, the endless report
    will be the result. AutoStop is automatically set to True when
    DataPipeline is set to nil, but it is possible to set it back to False.
    Check for instances in your code where you might have created this
    condition.

    Another thing to check is that all subreports in your report have their
    DataPipeline set. When a subreport does not have its pipeline set, you
    will sometimes see a condition where the first detail record prints and
    then you get blank pages.

    Another, non-data related cause can sometimes be your margin settings.
    If you have stretching bands that need to overflow to the next page, if
    your margins are too tight, sometimes the report engine will endlessly
    overflow to the next page trying to fit the overflow material.

    Still another cause might be having a statically positioned control, set
    to ReprintOnOverFlow, in the same band with a stretching control. For
    instance, if you have a memo set to stretch and in that same band, a
    label control set to ReprintOnOverFlow, then on every page after the
    first, the memo will begin to print after the label control. If the
    label is placed low enough that the memo has no room to print, the
    report will forever be trying to print the overflowing memo on the next
    page.


    --
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
This discussion has been closed.