CODEWITHSUNDEEP
visual-studiocrystal-reportssage-300
Husky
Husky

Reputation: 11

How to deploy VB.Net using Crystal Report on a PC that has Sage 300 installed?

I'm having issues installing an in-house application (VB.Net) we are making in Visual Studio 2022 with Crystal Reports SP32 on a pc that has Sage 300 2020 v6.7.0.80.

In the setup, we have included the Merge Module (CRRuntime_13_0_32.msm) in the setup. If we install this on a pc that does not have Sage 300, everything works good. The problem is when we installed it on the machine that has Sage 300, it caused Sage to stop working since they are also using Crystal Reports but of a different version. If we omit the Merge Module for Crystal, than our in-house application does not work when we try to open a Crystal Report in the application. Our in-house application is independent of Sage and does not interact with it.

How do we make a setup for a VB.Net application using Crystal Report without interfering with Sage 300?

We have trying including Crystal Report Merge Module in the Setup for our application. It makes Sage 300 not work after. We have tried excluding the Crystal Report Merge Module from our setup. Sage 300 works but then our application that uses Crystal Report does not work.

Any help would be greatly appreciated.

Thanks

Upvotes: 1

Views: 69

Answers (1)

MilletSoftware
MilletSoftware

Reputation: 4026

Below is a sample appName.exe.config for redirecting an application to use a different SAP runtime. You would need to adjust it to your scenario (e.g. what service pack level your app is on vs. the SP used by SAGE).

But a simple alternative solution is to make your app 64-bit. It would then use the separate 64-bit SAP runtime while SAGE is isolated to the 32-bit runtime. This only requires that the machine also supports 64-bit data connectivity. For ODBC, this boils down to simply adding a 64-bit ODBC DSN with the same name as the 32-bit ODBC DSN.

Here's a sample AppName.exe.config file content:

<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.CrystalReports.Engine" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportSource" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>    
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.Shared" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.Web" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.Windows.Forms" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.ClientDoc" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.CommonControls" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.CommonObjectModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.Controllers" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.CubeDefModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.DataDefModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.DataSetConversion" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>    
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.ObjectFactory" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.Prompting" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.ReportDefModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="CrystalDecisions.ReportAppServer.XmlSerialize" publicKeyToken="692fbea5521e1304" culture="neutral"/>
  <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
</dependentAssembly>   </assemblyBinding>   </runtime> </configuration>

Upvotes: 0

Related Questions