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

5 Subreports, Preview = 5 pages , when do viewer.Print , get 144 +

edited May 2002 in General
Hi

i have 5 subreports in a report, and swicth them off or on depending on what
has to be printed.

The report is being viewed in a viewer.

The report in the viewer is showing correctly but when i print , hundreds
of blank pages get spooled, and eventually my machine crashes.

I have set the whole report to have no Datapipeline, but the individual
subreports each have a pipeline assigned.

Any clues.

regards

Ian

Comments

  • edited May 2002
    ------------------------------------------------------
    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. As a test, try setting
    DetailBand.PrintHeight to phDynamic. A dynamic height band can overflow to
    additional pages as needed.

    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.

    --
    Cheers,

    Alexander Kramnik
    Digital Metaphors

This discussion has been closed.