I have a VS 2010 web project that displays reports using the ReportViewer. I have installed CR VS2010 SP 2. I am using an ADO.NET dataset as a datasource. The report has a background image that is 8.5 x 11 inches. I have several issues:
1. After adding the background image and moving it to the back then adding a field object, I am unable to select the field object by clicking on it. Clicking on the field object selects the background image. The only way to select the field object is to first select it in the objects dropdown on the Properties page then click the main report tab to put the focus back on the designer surface. This is very frustrating and time-consuming when there are a lot of fields.
2. After saving the report, closing it and re-opening it, the background image contents are gone. The image object is there but the contents aren't. Additionally, the report shows that it has been changed (asterisk in the title) even though no changes have been made.
3. Viewing the report with the background image and one field object for a datasource with 43 records in a web page using the CrystalReportViewer displays the report with no background image. Additionally, clicking the next page button results in a "Memory Full. Not enough memory for operation" error. I am setting the ReportDocument DataSource to a DataTable generated from a query based on user selections on a web page. In my report page, I have to store the Report Document in a session variable and set the ReportViewer report source on each postback (user selects another page) since the ReportViewer doesn't handle this internally.
4. In CR for VS 2008, I could declaratively set CrystalReportViewer.DisplayGroupTree to false. It appears that this property can no longer be set declaratively in CR for VS 2010 and must be set programmatically and this property is obsolete. Is there a better way to hide the group tree?
Issues 1 - 3 are critical and were also observed in CR for VS 2008. I posted these issues in this forum and it was suggested to install the service pack (which I did) or purchase the full version of CR 2008. It didn't make sense to purchase the full version of CR 2008 since it is already outdated. Instead I installed the SP 2 for CR for VS 2010 and created some test pages and the same report and observed the same behaviors.
I have preferred to use CR for my reporting needs for many years but trying to find solutions to these issues has cost me a lot of time. If I can't find solutions quickly, I will need to look at SSRS as an alternative.