Hi John,

Yes, this change was made in PB 2019 R3 because now a single PB IDE can target multiple runtime versions including even minor builds.  So for example, you can have one app compiled with PB 2019 R3 build 2670 runtime and another app compiled with PB 2019 R3 build 2703 runtime.  Here is more info on this change: https://docs.appeon.com/pb2019r3/whats_new/ch01s01s02.html

If you are having trouble managing the deployments manually, I really think you should consider to deploy using the PowerClient option that we added in PB 2019 R3.  It manages deploying not just the correct runtime files/versions but also will deploy your app itself including external files (images, OCXs/DLLs, INI, etc.) your app needs, and handles subsequent updates automatically.  Here is more info on PowerClient: https://www.appeon.com/products/power-client

Also, on a side note... I recommend you replace EasySOAP with the HTTPClient.  EasySOAP is obsolete feature that has not been enhanced in years and to best of my knowledge doesn't support TLS 1.2 security.  Here is tech article how to use the HTTPClient to call SOAP Web services: https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/236-call-soap-web-services-using-httpclient-object

Best regards,
Armeen