You should distribute PB 2019 R3 dll's to run an executable built with R3 and R2 dll's to run an executable built using R2. Also have in mind that in PB 2019 R3 all runtime files are not indicating the version of pb in their names. This was an enhancement related to decoupling ide from runtime and supporting different versions of the runtime (but only R3 runtimes - this is not available for previous releases). After that change pbvm190.dll is now renamed to pbvm.dll and is located to a different location than in previous versions. Example, in my computer I do have the following runtimes installed:
- C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 18.104.22.16870
- C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 22.214.171.12403
- C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 126.96.36.19928
When I work in an application through the IDE, I can choose wihch runtime to use to deploy my application.
Attention, this is a global setting, it will affect the IDE, so it means from the moment you change that value you have to restart the IDE, and from that point it will use the selected runtime version.
When building an exe you have to deploy that specific runtime for your application.
You can evaluate powerclient feature in pb 2019 r3 to make that work easier.
installers ask you to decide what folder to put the application in, so that 'requirement' would be a major bug.
you can either put the application and runtime in the same folder, or have the runtime in the system path, or use the xml file.