dataset performance poor after SP16

[former_member560462]

I have a legacy app, 32 bit, CrystalReports for Visual Studio, with a set of reports built against an Access (mdb) database. The select from the mdb is complex, 320 columns joining 10 tables. When we first converted this to CrystalReports for Visual Studio, connecting to the mdb directly, that failed with 'too many fields' error. Our solution was to extract the data from the mdb files and populate a .NET datatset, then use SetDataSource(dataSet) on the report. That worked great with SP16 and large datasets (10 tables each with 86400 rows), the report would complete in 15 minutes or so. Now we need to upgrade to SP32. This same report takes some 12+ hours to generate. I've tried a number of Service Packs going back to SP19 and they all take an excessive amount of time to generate this report. I've also tried to use an XML file as the source instead of a dataset but I see the same results: SP16 performs fine, later ones do not.

What changed between SP16 and later service packs to cause this? What can I do in my application to make this perform as it did before?

[former_member11696 · Accepted solution]

You will need to build a DataSource dll to be able to use it in CRD.

On the CR for WIKI get the Parameter test app, it has the ability to update to your data source.

CR for VS is version 13, CR Designer is version 14 and has no usable dll's in an application.

[former_member11696]

Lots of changes, you read about them all here:

https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads

Set the build to 64 bit and see if that helps.

What happens in the standalone CR Report Designer?

[former_member560462]

Thank for your attention. It appears that this issue was introduced in SP19. SP18 shows good performance in my testing, SP19 does not.

A review of the fixes/enhancements/known issues for SP19 would be the relevant document and I'm not seeing anything in there applicable to this.

A 64 bit is just not feasible for our application and seems unlikely to be of help.

As for the standalone CR Report Designer (CR2016 is what we use). I don't know how to create a datasource that is a dataset with this. Is that even possible? However, I can set up a datasource that is my XML file. Regardless of SP16, SP18, SP19, SP32 when I 'refresh data' it looks like its reading about 2 records/second. That's a very long time.

With regards to the standalone CR design (CR2016). It is running very slowly for me importing this data, but I note that the only Crystal module it appears to be using is crdb_adoplus.dll which it finds in a different location that my CRforVisualStudio install does.

The CR2016 lives in C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86

It has file version 14.0.2005.2618, product version 14.2.5.2618

while the CRforVisualStudio SP18 lives in C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86

It has file version 14.0.2018.2192, product version 13.0.18.2192

So I don't think we are comparing apples to apples with this.