showing + hiding regions --> infinite pages!!!

rbuser

Hi!

I generate all my report builder reports at the code-level which works
very well. I now needed 3 regions to be some sort of header for 3 detail
(sub-)reports. in the BeforePrint-Event I show or hide these regions, so
I don't have to repeat headers that are the same. The problem is that
ReportBuilder has a problem with the pagebreak and somehow stops showing
the report and just shows plain blank pages! this goes on forever,
litarally. Pressing the ">>" button ends in an endless loop counting
blank pages....

any help? this is obviously a bug!

thanks,
Tom.

digitalmetaphors

See the guidlelines below for possibilities on why the report could be
producing endless pages.

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

rbuser

the problem couldn't be solved with any of your guidelines... instead, David
McNeill solved it (.public.reportbuilder.subreports): I had to set the
StopPosition property to something like PaperHeight - MarginBottom - ..
no it works!!

"Alexander Kramnik (Digital Metaphors)" schrieb: