report writing 6000 pages

rbuser

There is a 3 page report that when it is sent to print start printing blank
pages and when printing it state that is a report of over 6000 pages. (
example: page 1 of 6000) My client called me and told me that the report was
working well but from a given date it started to print all those blank pages
without any reason.

What can I do?
Delphi 6 RB 6.03

Carlos

rbuser

Maybe it's simular to a problem I had. A report of mine went crazy, and
just produced emty pages for infinity.
The problem was that the Header,Detail (static) and Footer -band together
with the margins settings did NOT fit on the page (A4)
By reducing the size of the band and adust the margins it was OK.

På Mon, 4 Aug 2003 17:05:30 -0300, skrev Carlos :




--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

nicocizik

Hi Carlos,

Trond, is correct. Here is an article that may 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.


--