Great question Don Moore.

My organization is going to be doing the same thing.

This is helpful.

Thanks,

Bill

Thank you Chris and Michael.

Your replies were exactly the information (confirmation) I was looking for. After 48 years in software development (in an extremely wide variety of languages and environments), I do know that there are usually no shortcuts, but it was worth a try. Thanks again, especially for the rapid response! We're looking at migrating 9 or so PB applications (along with some Apex applications, Crystal Server interfaces, secure file exchange server interfaces) spread across 3 Oracle servers with 500 - 1000 users, ”in house” and through Citrix, and I can now inform management of the extent of the work and timing involved to accomplish this task. I will grab another computer, consume another Appeon license and keep my Release 2 and Release 3 development environments separate. As for the actual migration, I expect that it will be straight forward, simple, fast and issue free, just as it was going from v12.6 to 2017. LOL, I may end up retiring on this one (as it is just me)!

Re 1) Across releases the filename remains identical while internal version number changes. PB IDE defaults to install into same folders across releases of same version. So files overwrite prior versions. Example:

• File = PBDWE170.DLL is DataWindow Engine's main runtime file
• In my current install it has version number = 17.2.0.1915 where
  • 17.0 = PB 2017 GA
  • 17.1 = PB 2017 R2
  • 17.2 = PB 2017 R3
  • 1915 = Build number
• In my install I also have file = PBDWE190.DLL with version number = 19.1.0.2279.
  That version + build is customer beta of PB 2019 R2.
• PB docs state we can expect same number scheme to continue at least through PB 2019 and its releases

Re 2) Never run a PB app on a different runtime version than it was compiled for!

• That is true for new releases that change runtime's feature set.
• That is also true for new patches/EBFs since a bug fix or security fix could mean compiler change. Hence, that fix only applies after a recompile.

Reason for this restriction even for bug fixes => Any bug fix may be a fix to the compiler or both compiler + runtime. Such fix is only "live" after new app deployment.

I remember teaching that rule from PB3 onwards. Make it a habit to be on the safe side.

HTH /Michael

Hi Don;

1) YES. However, after that installation - please install MR #2170 to be O18C/19C compliant.

2) Since PowerSoft's PB version 1.0 - always do a Full Build and then recompile after any update so that the generated code in the EXE and PBD's match your new run-time DLL's (PBVM). Otherwise, unpredictable behaviour may occur.

3) PB2017R3 build 2170 will work with either O18C or O19C DB Client drivers in 32bit or 64bit mode. Note that the IDE and PowerServer ToolKit require the 32bit drivers but your 64bit PB App EXE's and PowerServer will require the 64bit Oracle DB Client drivers.

HTH

Regards ... Chris