1. mike S
  2. PowerBuilder
  3. Saturday, 29 August 2020 17:28 PM UTC

In old versions of PB there was no need to register the sybase excel dlls for their .net excel save as. This appeared to have changed sometime between 12.6 and 2017R3.   

I've seen some conflicting information on whether it supposed to be required to register those dlls into the GAC.  (typical installation methods would include runtime dlls with exe, gac registration should be required only if those dlls are stored elsewhere).

The bug fixes for build 2323 do not list anything about the GAC requirements changing, but a response to a bug report seems to indicate that starting with 19R3 build 2323 the GAC is no longer required?

** edited for brevity:

following text was edited for brevity, click here to see original in context

"BTW, the issue is fixed in the PB 2019 R2 Build 2323: 
copy the Sybase.PowerBuilder.DataWindow.Excel12.dll to your application folder
and don't using the GAC install and try it again."


 

Accepted Answer
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Saturday, 29 August 2020 19:36 PM UTC
  2. PowerBuilder
  3. # Permalink

Appeon didn't modify this DLL in the 2017 version so my best guess this was either changed in PB 12.6, which Appeon versions of PB are based on, or it may be behavior change of updated Windows OS.  Anyway, per the ticket Appeon has made modification to this DLL so if you upgrade to PB 2019 R2 then registering will not be required.

Comment
  1. Chris Pollach @Appeon
  2. Wednesday, 2 September 2020 15:03 PM UTC
Hi Armeen;

Yes, its still the same requirement as in PB 12.x. If you copy the "Sybase.PowerBuilder.DataWindow.Excel12.dll" to your App's EXE folder then that is all you need to do for the deployment.

If you install the "Sybase.PowerBuilder.DataWindow.Excel12.dll" to a *different* folder other than the PB App's EXE - then you must register the .NET DLL in the GAC.

Regards ... Chris
  1. Helpful
There are no comments made yet.


There are replies in this question but you are not allowed to view the replies from this question.