on 2023 Aug 10 4:54 PM
Good catch on the runtime installer difference.
Check the Platform Database clients support in CR 2020 from here:
https://wiki.scn.sap.com/wiki/display/BOBJ/SAP+Crystal+Reports+-+Supported+Platforms
Look for the Database info, it then downloads an Excel file with the supported Clients.
Is this a Desktop or WEB App?
CR runtime is set for your Application Platform and not the OS.
ClickOnce installs both x86 and x64, so if you have your Project set to AnyCPU it's likely trying to run in 64 bit mode which the App.Config or Web.Config file may be redirecting to the wrong location.
And see my Blog on upgrading your Project, a recompile is required. Make sure Copy Local is set to False, mixing versions in your \bin folder will cause problems.
There is one update issue, ADO.NET (XML) database dll was reversioned form 14 to 13, that required a repair install. So if your customers are using an older version there is no way around this other than a repair or clean install.
See the WIKI for Fixed Issues, I believe the dll version change was around SP 26, so if you old runtime version is a previous version that could explain why you need to do a repair install with the MSI.
https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads
You should be setting your installer to uninstall first and then install SP 34, good practice...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
71 | |
10 | |
8 | |
7 | |
7 | |
6 | |
6 | |
6 | |
6 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.