ReportViewer with over 400 pages

[Former Member]

I have a report that has 500 pages. the viewer is taking over 5 minutues to render the report. Is there anything that can be done to improve the load time.

using Visual Studio 2008.

In debug mode, the problems seems to be the rendering of the report in the viewer control. The report gets binded to the reportview in about 1 minute, but then the page takes another 5 minutes to render the report.

[former_member183750 · Accepted solution]

What version of CR are you using? If this is a stand-alone version of CR, how long does the report take here?

If you are not using a stand-alone version of CR, it may be helpful to download ann eval of CR 2008 from here:

http://www.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx

If the report takes an equivalent time there, there will not be much else to do at runtime.

Any updates applied for your version of CR?

Ludek

Follow us on Twitter

http://twitter.com/SAPCRNetSup

[Former Member · Accepted solution]

we just purchased crystal 2008 desktop and server. the latest service packs are loaded. we are upgrading from crystal reports 8 (active-X control) to the .NET control. I am very new to crystal report development and learning as I go.

I am using the crystal report viewer bundled with Visual studio 2008.

what report should I view?

the problem with this one report is I am setting a parameter to 3,000 values. but the problems seems to be related to rendering the report (displaying it)

here the code:

report.SetParameterValue(0, listOfString.ToArray())

-listOfString has about 3000 unique values

[Former Member · Accepted solution]

I have a one page report (another report) and the report does not display on the screen unless I hit the zoom button.

the report defaults to 100% and shows a blank screen. if I change the zoom or export the report it shows the data.

[former_member183750 · Accepted solution]

Wow. 500 page report, 3,000 parameters takes 5 minutes? I'd take that and run.

Other that throwing [Service Pack 2|https://smpdl.sap-ag.de/~sapidp/012002523100009038092009E/cr2008win_sp2.exe] on it,

I have no other suggestions. I think a 5 minute + generation will be about as good as it will get.

You may want to consider building an ADO .NET dataset off of the parameters and passing that to the report.

Ludek

Edited by: Ludek Uher on May 10, 2010 1:34 PM

[Former Member · Accepted solution]

just tying to convert the reports over. not my original design.

*You may want to consider building an ADO .NET dataset off of the parameters and passing that to the report.*

that how I load the 1000's of parameters.

Edited by: Andrew McCormack on May 10, 2010 10:36 PM

[Former Member · Accepted solution]

What about the zoom problem? first time I seen that happen.

the report is one page.

to view the report I need to zoom to 80% than back to 100%.

[former_member183750 · Accepted solution]

As per the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] keep to one issue per thread. Otherwise these things get messy real quick.

Ludek

[former_member183750 · Accepted solution]

I don't know. This report / solution sounds weird. You may want to create a phone case and discuss it with someone.

Phone cases can be created here:

http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryI...

Ludek