Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved PB2019 install with PB2017

  1. Advice
0
Votes
Undo
  1. Brad Mettee
    Brad Mettee
  2. PowerBuilder
  3. Thursday, 13 June 2019 03:51 AM UTC

 

Does anyone know of any issues because of duplicate, but newer, files shared between PB2019 and PB2017?

Different files in the shared\powerbuilder directory are:

atl80.dll
libeay32.dll
libglog.dll
libjcc.dll
libjtml.dll
libjutils.dll
libsybunic.dll
nlwnsck.dll
pbchkweb.dll
pbvsx_plugoutlib.dll
pdc32.dll
spell32.dll
ssgp.dll
ssleay32.dll
ssts.dll
txml2.dll
xerces-c_2_8.dll
xerces-depdom_2_8.dll
x64\libjcc.dll
x64\sybase.powerbuilder.datasource.db.dll
x64\sybase.powerbuilder.datawindow.excel12.dll
x64\xerces-c_2_8.dll
x64\xerces-depdom_2_8.dll

These appear to be the only common files between PB2017 and PB2019.

There's a discrepancy between versions of one of the 64bit files in PB2019 within itself. In PB2019, the sybase.powerbuilder.datasource.db.dll file exists in Program Files (x86)\Appeon\PowerBuilder 19.0\DotNet\bin\x64 and Program Files (x86)\PowerBuilder 19.0\DotNET\bin\x64, have the same date, but differ in size. In PB2017, the files in equivalent locations are identical.

 

 

  1. DLL
datawindow report. 1st page portrait, 2nd landscap...
Compiling Powerbuilder Using Orca DLL
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 13 June 2019 16:21 PM UTC
  2. PowerBuilder
  3. # 1

Hi Brad;

  Yes, you have always had to watch out for the shared files between PB versions that are not uniquely named!

I typically avoid this conflict by making sure that ...

1) All PB paths in the O/S system path are from the highest PB version to the lowest. Normally, the shared DLL's of the same name are downward compatible. So my System Path is currently PB2019, 2017, 12.6, 12.5.1, 12.1 and 11.5.1 and all IDE's are working well together for me.

2) The other thing you can do after a PB version is installed is to move the PB version's path to an environment  name and then use these in the System Path using #1 above's order. Then, you can comment out the IDE(s) that you are not using by changing the environment variable's name. I use for example PB2017 and then rename that to PB2017_XX and vise versa to enable / disable various releases I want to make sure do not interfere with the PB version that I am using currently. For example:

System Path ...

 

HTH

Regards ... Chris

Comment
Brad Mettee
  1. Brad Mettee
  2. Thursday, 13 June 2019 18:02 PM UTC
Since we skipped major versions of PB, we've never run into the "common file" problem (or maybe we did and never knew it). Versions we've used over the years are: PB 3, 5, 8, 10, 12, 17, 19.



Thanks Chris
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.