Hi.

One thing that Appeon implemented in PB 2019 R3 was to decouple runtimes from IDE. You can find information about this changes to the following link:

Decoupling Runtime and IDE - - What's New (appeon.com)

As a result of this change, version information was removed from dll's filename. So it's normal to see that pbvm170.dll (or pbvm190.dll from 2019 R2) is renamed to pbvm.dll.

Of course this can be confusing. But in the end I believe that it is a more flexible way of doing things. Of course there are limitations, example you cannot deploy an application built with pb 2019 R3 with one built in pb 2021, with their runtimes on the same folder, because they do have different runtimes but their filenames are identical. But you can install those runtimes to a different location and set the executables to look for them at the correct location (there is an xml file that you can modify to do that).

One last thing, pbacc170.dll is part of PB's 2019 R3 runtime and is called pbacc.dll. You also have an pbsnc.dll... If you don't find them then take a look to the folder where the runtimes are installed on the machine where PB is installed (for me it's C:\Program Files (x86)\Appeon\Common\PowerBuilder, and there are some folders - at least one - called Runtime 19.2.0.xxxx. If you also installed PB 2021 you should have folders like Runtime 21.0.0.xxxx). If some dll's where missing from msi produced with dll packager then check that the appropriate options were checked before creation.

Andreas.

You will find a helpful breakdown of the various PB runtime DLL's in PB Help (F1 from within the IDE) if you switch to the "Index" tab and enter "runtime files" as the search keyword.

Hi;

 Yes, the DLL numbering was dropped in PB2019R3 as documented in the PB Help "what's new" due to the runtime now being decoupled from the IDE. 

  Unless your still running older PB2017R3 apps, you can delete all the Xxxxxx.170.dll files.

Regards ... Chris 

In our machine we have installed both PowerBuilder 2017 R3 and PowerBuilder 2019 R3 versions

Let me explain my doubt through an example.

pbacc.dll - Used by 2019 version PB
pbacc170.dll - used by 2017 version PB

The PB will be able to identify the appropriate dll file based on the dll name.

But for dll files such as libjcc.dll, Sybase.PowerBuilder.DataWindow.Excel12.dll etc. which have common dll name for 2017 and 2019 versions, If any problem will occur in our case where we have installed both versions of PB (2017 and 2019) in same machine as mentioned above. If yes, then what will be the solution?