master-detail report not printing 2-page items

rbuser

The tools are Delphi 4 and ReportBuilder 4.07Pro

What happens is a have encontered 2 separate applications that are using a
master-detail report. These mater dataset can have multiple rows, which is
a multi-page report each one with its own details.

The problem is if the details in one of the "master-items" are not fitting
one page ( and printing on a second page), all the pprints after that is
non-stop garbage pages (apparently prints non stop that second page from
the problem item).

Thank you in advanace to anyone who took the time to read this.

Be well,
Cristian C.



--- posted by geoForum on http://delphi.newswhat.com

nicocizik

Hi Cristian,

You are using a somewhat older version of ReportBuilder which may have had
an issue with this type of report. Perhaps the following article will help.

------------------------------------------------------
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.


--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com