Hi Olan;

  For the IDE - R2 & R3 cannot co-exist. I used to have a little Chris trick to make any two minor versions work on the same PC. I've been using that trick since PB 3 and throughout the Appeon PB series but it does not work with R2 & R3 (starting with R3's decoupled runtime). So the solution that I use is  ow is to use two PC's - one for <=  R2  - any combination of PB releases in the Sybase or Appeon 2017/2019 series. The other way I also solved this was to install a W10 VM on the same PC as R2 and only install R3 on the VM (no R2).

  The deployed PB App EXE's run time is not a problem. I typically use one of these two approaches...

1) Place the PBVM run-time DLLs in the same folder as the EXE     // OR

2) Create a BAT file to launch the PB App EXE but first amend the "System Path" to point to the correct PBVM version. Since the PB App is started from a BAT File, the System Path is unique (local) to that BAT file. Thus, each PB App EXE can now point to its own PBVM version (location) as required.

Food for thought.  HTH

Regards ... Chris

Hi Olan,

No, two minor versions cannot co-exist.  You will need to set them up on two separate physical machines or VMs. 

Starting with PB 2019 R3, minor versions of the PB runtime can co-exist, and a single PB IDE can deploy to multiple runtimes.  Here's more info: https://www.appeon.com/products/powerbuilder?tab=gb4ao2id42&ct=t(PB2019R3)#newinr3

Best regards,
Armeen

Hi Olan,

I don't know where, but I think I read you cannot have both 2019 R2 and R3 on the same machine.

Correct me if I'm wrong anyone.

regards.