ReportBuilder hangs at report with regions and memo fields
Hello there,
we have got a problem with the ReportBuilder 14 & 15.
We are using a report for printing an invoice which is built like this:
The detail band contains four groups. The detail band in the fourth
group contains four regions. Each region contains several labels and
memo fields. For all the regions and the memo fields the Stretched
property is set to True.
The code of the Report (GroupHeaderBand.BeforePrint) turns the regions
visible or invisible depending on the type of the invoice.
This works quite well, however with some invoices the ReportBuilder
fails to render the report:
In preview mode (also in the preview mode of the report designer tool),
the first page of the output is rendered, but after that the page
counter runs up infinitely.
When trying to print the invoice on paper, ReportBuilder hangs at the
"Accessing data" window.
The error does occur with some invoices only, but we cannot see what
exactly causes it.
Thanks,
David
we have got a problem with the ReportBuilder 14 & 15.
We are using a report for printing an invoice which is built like this:
The detail band contains four groups. The detail band in the fourth
group contains four regions. Each region contains several labels and
memo fields. For all the regions and the memo fields the Stretched
property is set to True.
The code of the Report (GroupHeaderBand.BeforePrint) turns the regions
visible or invisible depending on the type of the invoice.
This works quite well, however with some invoices the ReportBuilder
fails to render the report:
In preview mode (also in the preview mode of the report designer tool),
the first page of the output is rendered, but after that the page
counter runs up infinitely.
When trying to print the invoice on paper, ReportBuilder hangs at the
"Accessing data" window.
The error does occur with some invoices only, but we cannot see what
exactly causes it.
Thanks,
David
This discussion has been closed.
Comments
This is not a known issue with ReportBuider. My first suggestion would
be to start hiding(Visible := False) report components and commenting
out any relating event code until the affected report runs correctly.
Then begin adding items back until the issue occurs to isolate the problem.
When you find the problem, please send a simple example that
demonstrates this to support@digital-metaphors.com in .zip format.
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com