Spoolfile for a printer of many pages

rbuser

Hello,

In a aplication we are using Report Builder for printing labels. When
printing labels by one of our customers we have a problem.
Sometimes when printing for example 3 labels, each on a different page, the
spoolfile for the printer contains more than 20000 pages while it is still
spooling more pages to the printer. The printer the customer is using is a
Intermec EasyCoder 7421 delivered by PhiData.

The paper size is a custom defined size with a width of 105 and a heigh of
63.

I have seen that when the total height of the report is greater than the
paperheight this problem will occur. But by our customer the total height of
the report is smaller than the paperheight, so this cannot be the reason of
this problem.

The question is what can be the cause of this problem, so I can fix the
problem for the customers.

regards

Hanjo Willems

nicocizik

Hi Hanjo,

The following article may help with this issue.

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

--