Only some report can be run on CRAXDRT9 vs. Crystal Reports 2011 Developer.

[Former Member]

Hi, and Thank you in advance for your help.
I have generated and used many Crystal reports that I created in Crystal Reports 2011 Developer - all of which run perfectly well from CR 2011. However, I am automating the generation of these reports in MS Access VBA using Crystal Reports 9 ActiveX Designer Run Time Library (CRAXDRT9), and most with the exception of three will run. The error that is returned: Run-time error '-2147189166 (80047e52)' Failed to open a rowset. Details: 42000[Microsoft][ODBC Microsoft Access Driver] Syntax error in FROM clause. When I debug it chokes on ReadRecords. Oddly, two of the three are only looking at one datasource, which is also successfully used in most of the other working reports.
I am stumped. Can you help?

[Former Member]

Is there a Crystal for VS Code?

[former_member11696]

Hi Kurt,

Brian is correct, likely some new feature in CR 2011 the old RDC engine can't handle.

And unfortunately RDC 9 has not been supported for 10+ years. Time to upgrade...

CR XI R2 was the last version that still supported the RDC.

What you really need to do is upgrade to VS 2010 -> 2015 and convert your app to CR for .NET.

You can get the runtime from here:

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

Support all version of reports but recommended to update the RPT files to CR 2008 and/or above.

There is not direct conversion from COM to .NET so you will need to redesign your application CR part to use .NET components. Mostly the front end part of your app can be converted to Managed .NET, mostly...

Link above has all sorts of sample links also.

And post your questions to the CR for VS tag:

https://answers.sap.com/tags/01200615320800001270

Don

[Former Member]

Hi Brian.
I am using Access 2016. The 3 reports that are failing were created in 2011.

Which VBA app works best in this situation?

I will try what you recommend and see if I can determine what is causing the hiccup.

[former_member292966]

Hi Kurt,

What version of Access are you using?

The 3 reports that are failing, were the created in Crystal 2011 or were they upgraded from Crystal 9?

The reason for this error is probably because these reports are doing something that version 9 isn't capable of or doing something that 2011 changed sometime after 9.

If you want to troubleshoot, the only way would be to remove one table and try it in your VBA application until it works. Then you can move forward again and see what is different between this report and one that does work.

The best suggestion is to upgrade your VBA application. The differences between 9 and 2011 are huge. You could make sure you have the latest updates for 2011 but I think you'd save yourself a lot of work down the road by upgrading your application.

Brian