Prev: 4 days and still can't get my report to depoly (help)...
Next: Native compiler return value 128
From: Duncan Bayne on 2 Oct 2007 00:18
Hi,

Our app uses the LocalReport object to render a report in RDLC format
to PDF. This works nicely, until we add several very large images to
the report. At this stage, we see the following exception:

Microsoft.Reporting.WinForms.LocalProcessingException was unhandled
Message="An error occurred during local report processing."
Source="Microsoft.ReportViewer.WinForms"
StackTrace:
at
Microsoft.Reporting.WinForms.LocalReport.InternalRender(String format,
Boolean allowInternalRenderers, String deviceInfo,
CreateAndRegisterStream createStreamCallback, Warning[]& warnings)
at
Microsoft.Reporting.WinForms.LocalReport.InternalRender(String format,
Boolean allowInternalRenderers, String deviceInfo, String& mimeType,
String& encoding, String& fileNameExtension, String[]& streams,
Warning[]& warnings)
at Microsoft.Reporting.WinForms.LocalReport.Render(String
format, String deviceInfo, String& mimeType, String& encoding, String&
fileNameExtension, String[]& streams, Warning[]& warnings)

Although we can handle this exception gracefully within our
application, it'd be nice to know what the limits are for the
LocalReport object in terms of data size, and whether there're any
techniques we could be using to minimise the memory footprint of our
reports, so as to reduce the chances of this exception being thrown in
production.

TIA for any advice.

Yours,
Duncan Bayne

 | 
Pages: 1
Prev: 4 days and still can't get my report to depoly (help)...
Next: Native compiler return value 128