Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jul 13, 2007 12:30 PM by OhioSteve
Jul 13, 2007 12:30 PM|LINK
I have an asp.net web page that uses the reportDocument class. I declare and instantiate a reportDocument called r. Then I export it to the http response object using this command:
r.ExportToHttpResponse(ExportFormatType.PortableDocFormat, System.Web.HttpContext.Current.Response, False, "")
For most of my reports this works great! The report appears in a web page almost instantly.
However, I have one report that is a real monster. It analyzes 250,000 records and creates a crosstab. This report takes 63 seconds to run on my workstation using my personal copy of CR.
Unfortunately, it takes SIX MINUTES to execute "r.ExportToHttpResponse...." for this report on the web server. However, when it finally does finish, the report's data is accurate.
I suspected that somehow CR was trying to export the underlying data, not just the image of the crosstab. So I tried three different times to stop that behavior. I tried each of the three lines below (separately) but none of them worked.
r.ReportOptions.EnableSaveDataWithReport = False
r.ReportOptions.EnableSaveSummariesWithReport = False
r.ReportOptions.EnableSaveSummariesWithReport = True
I really want to pound down that execution time from six minutes to one minute. I look forward to your feedback on this issue.