CRRuntime_32bit_13_0_13 with reports developed in CR2016

[former_member614482]

Hi,

Our application (Developed using PowerBuilder) is using Crystal reports for reporting purpose.

We have used VS2010 to implement Crystal Reports i.e Installed CRRuntime_32bit_13_0_13 in developer machine and then added necessary assembly files like CrystalDecisions.CrystalReports.Engine. Then added to code to read and open, print crystal reports. Finally we generate one single DLL file from Visual Studio 2010 and that is being consumed by our PB application.

In Windows assembly folder, the version of %CrystalDecisions% file is (General Version:13.0.2000.0 and File Version: 13.0.13.1597)

We created new crystal reports (.rpt) using SAP Crystal Reports 2011 and able to run report via our PowerBuilder application and ofcourse the powerbuilder application using the solution implemented using VS2010.

In Production , users will install our application (developed using PB) and also CRRuntime_32bit_13_0_13.MSI so that they can view all the Crystal Reports. All going good and no issues.

Question:

The customers want to create their own crystal reports using SAP Crystal Reports 2016 (consider they don't use any exclusive features available in CR2016). Will they be able to run those reports developed using CR2016 with the same run time CRRuntime_32bit_13_0_13 which we are supplying ? Kindly refer the content above my Question to understand how we have used VS2010 and CrystalDecisions assemblies to incoporate Crystal reports into our application.

Thank You,

Ganesan

[former_member11696 · Accepted solution]

Hi Ganesan,

I suggest you upgrade to SP 25 so you have all of the latest runtime and supported runtime.

The problem is CR 2016 SP 4 and above uses the latest security plug-in dll's, there is a known issue if you try to use that version of CR with a lower version of CR for VS runtime than SP 21 you will get a runtime error. CR for VS SP 13 still uses old dependencies also, Microsoft no longer supports them.

You can get them from here, and all of the latest info:

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

Don

[former_member614482 · Accepted solution]

Thank you Don. Should we always take latest Runtime and compile/build (after removing old and adding latest Crystal assemblies from GAC) our code whenever new Runtime is released? Because it involves testing effort to check whether report retrieval and printing is working properly from our Powerbuilder application. Your inputs will be much appreciated.

Thanks in Advance

Ganesan

[former_member11696]

You don't really need to update to date each time, we release them 4 times a year.

But if you run into issues then first thing is to update. It will usually have the latest support for current OS and client updates etc.

Don

[former_member614482]

Thank you for your Help!!

Ganesan