ActiveX Printer Error when print large number of page

[Former Member]

Hi,

I have this problem when developing the report on my project.

I developed the Crystal Report embedded in Visual Studio 2008 to be displayed in web form.

I'm using .NET and the operating system of the development computer is Windows 7 32 bit.

The problem is, I have a quite complex report displaying the statement for the customer which is result in 209 pages.

When the report has successfully loaded, I simply click the print icon and it comes up with the error "A communication error occurred. Printing will be stopped"

But, after that...I tried something different, when the report has successfully loaded, I went through the report by moving for every 30 pages until it reaches the last page and click the print icon. and it prints without any errors!

Anybody knows what caused this?

By the way, I'm using the ActiveX printing mode for the Crystal Report.

Thanks

-Marry-

[former_member183750 · Accepted solution]

I'm thinking there is something not processed in the report so forcing the report to process everything up to the last page before printing may help. Try the following code before sending the report to the viewer:

Dim prc As New CrystalDecisions.Shared.ReportPageRequestContext

rptDoc.FormatEngine.GetLastPageNumber(prc)

This may slow down the time it takes for the report to come up as the whole report will need to be processed, formatted, etc.

Also, make sure you have SP 1 for CR 10.5:

https://smpdl.sap-ag.de/~sapidp/012002523100009351512008E/crbasic2008sp1.exe

Ludek

Follow us on Twitter http://twitter.com/SAPCRNetSup

Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

[Former Member]

Hi Ludek,

I have no luck with the SP either.

The report has made my laptop shut down twice

And we decided to create workaround by creating a form that listed the report and then print it one by one using background process.

Thanks for your help anyway.

-Marry-

[Former Member]

Hi Ludek,

Thanks for your response.

I think forcing the report to go to the last page is not the best option since I heard from my colleague that going directly to the last page will give the error on the report too and also the report has taken a long time to execute already.

I'll try to update the SP of the CR and will let you know the result.

Thanks

-Marry-