1. Andreas Mykonios
  2. PowerBuilder
  3. Thursday, 4 November 2021 15:32 PM UTC

Hi.

I always remember we were said that when we deploy an executable the accompanying runtime should be the exact same release to avoid instability. Is this still the same? I ask because while reading help file we are a little confused. It is stated for example that:

“The application executable can run against PowerBuilder Runtime at the same or later versions, for example: Application executable compiled with Runtime 2019 R3 2019 Can run with Runtime R3 or later and Cannot run with Runtime 2019 R2 or earlier” (Topic: Selecting a version of PowerBuilder Runtime).

This mean that if we build an application using 2019 R3 2670, we can run it with 2019 R3 2728 and feel secure that everything will be ok?

Andreas.

Accepted Answer
Julie Jiang @Appeon Accepted Answer Pending Moderation
  1. Friday, 5 November 2021 07:17 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Andreas, 

Actually, your understanding is correct based on the documentation, "if we build an application using 2019 R3 2670, we can run it with 2019 R3 2728 and feel secure that everything will be ok."  

However, Chris is more correct. It is best practice to never execute a PB App EXE that as compiled with version X with runtime Y. Unknown behaviours and instability can (not could) occur. Our engineer and writer was too optimistic when providing the second table, "Selecting a version of PowerBuilder Runtime for the application executable". After more discussion, we plan to withdraw the table from the document, and still suggest that PB App EXE that as compiled with version X shall work with runtime X.  

Thanks for catching this documentation issue.  We will make correction in the next release, and also explain this as a known issue in 2021 GA Release Notes.

Best regards, Julie

Comment
  1. Armeen Mazda @Appeon
  2. Tuesday, 9 November 2021 15:52 PM UTC
Chris is exactly right!
  1. Helpful 1
  1. Andreas Mykonios
  2. Wednesday, 10 November 2021 08:39 AM UTC
Hi Julie.



I would suggest to issue a white paper while the help file and manual are not updated. There was a bug reported from me (https://www.appeon.com/standardsupport/track/view?id=6520) in 30 April, 2021. There I was pointing that this part of help was misleading. While Reading even the first table, you get the idea that you can change from one of the supported runtimes to another at any time. But this is not true for major releases. You cannot go back from a 2021 runtime to a 2019 runtime. And it's not clearly stated.



This part of help should be very clear because you never know the experience of the person reading it. And this should be also added to 2019 documentation, which by the way is identical (don't forget that many people prefer to remain in the LTS version).



Andreas.
  1. Helpful
  1. Julie Jiang @Appeon
  2. Thursday, 11 November 2021 01:10 AM UTC
Hi Andreas,

It is a great idea. Thank you. We will try to create a whitepaper about the compatibility between different versions, and different products soon.

Best regards, Julie
  1. Helpful
There are no comments made yet.
Julie Jiang @Appeon Accepted Answer Pending Moderation
  1. Friday, 5 November 2021 07:22 AM UTC
  2. PowerBuilder
  3. # 1

Hi Armeen, 

We have two tables at https://docs.appeon.com/pb2021/application_techniques/ch09s02.html#Selecting_a_version_of_PB_Runtime. The one you pasted is about the compatibility of PB IDE and PB Runtime versions (The first table).  I believe Andreas is double checking on the second table, "Selecting a version of PowerBuilder Runtime for the application executable", and his understanding looks correct to me. 

Best regards, Julie

Comment
  1. Andreas Mykonios
  2. Friday, 5 November 2021 08:30 AM UTC
Hi Julie. That's exact. I was mentioning the second table. This one is misleading.

Thanks.

Andreas.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 4 November 2021 16:19 PM UTC
  2. PowerBuilder
  3. # 2

Hi Andreas,

The situation is as before that the .EXE version and runtime DLL version needs to match.

What has changed is now the version of the PB IDE and runtime do not need to match.  In other words, the PB 2021 IDE can compile not just for PB 2021 runtime but also 2019 R3.

The following table shows the compatibility...

IDE (including MRs)

Supported Runtime (including MRs)

Unsupported Runtime

2019 R3

2019 R3

2021 or later

2021

2019 R3, 2021

2022 or later

2022

2019 R3, 2021, 2022

2022 R2 or later

2022 R2

2019 R3, 2021, 2022, 2022 R2

2022 R3 or later

2022 R3

2019 R3, 2021, 2022, 2022 R2, 2022 R3

2023 or later

So long story short, basically you can update your PB IDE to the absolute latest version yet still maintain apps on older version of runtimes or multiple projects that each are using different runtime versions.

Best regards,
Armeen

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.