Problems after RB-Update
Hi
We have updated report builder from version 4.23 to 6.01. Now we have some
problems
- some reports are running endless (100.000+ pages), before they worked
correct.
- some reports are now over two and more pages, before there was only one
page.
The same hardware, the same printer, I've only updated the report builder
files.
I use Delphi 5.0 fon W2k.
What has changed from version 4.23 to version 6.01 ?
Is there a converter / updateprogramm for the old report files (*.rtm)
avaible ?
J?rgen
We have updated report builder from version 4.23 to 6.01. Now we have some
problems
- some reports are running endless (100.000+ pages), before they worked
correct.
- some reports are now over two and more pages, before there was only one
page.
The same hardware, the same printer, I've only updated the report builder
files.
I use Delphi 5.0 fon W2k.
What has changed from version 4.23 to version 6.01 ?
Is there a converter / updateprogramm for the old report files (*.rtm)
avaible ?
J?rgen
This discussion has been closed.
Comments
that should help you figure out why your report is generating endless pages.
As far as the reports which are generating multiple pages go, why are they
multiple pages? That is, which control are taking up more space? Are the
memos printing longer? Is there more white space, ect?
--
Cheers,
Alexander Kramnik
Digital Metaphors
------------------------------------------------------
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.
http://www.digital-metaphors.com
info@digital-metaphors.com