1. Marc Wietscher
  2. PowerBuilder
  3. Wednesday, 20 November 2019 14:02 PM UTC


will it be possible to use PB2019 R2 and any release of PB2017 simultaneously on the same machine?

First release of PB2019 could not be started while an instance of PB2017 was still running on the same machine, stating that licence was still logged in.

Though it is possible to have several instances of PB2017 OR PB2019 opened and logged in at the same time, this does not work for instances of different PB versions.

Neither using auto log off and auto log on functionality that was added to PB2017 R2 or R3 nor buying another 55 licences for our developers will be an option for us.

We have to maintain several releases of our software that was built with different versions of PowerBuilder (PB8.0, PB10.5, PB2017). Usually bugs need to be fixed across multiple releases. So switching between PB instances of different versions on the same machine is essential to us! And I don't see why this would be a technical or legal issue considering Appeon's licencing technique.

In another post (https://community.appeon.com/index.php/qna/q-a/can-2017-r2-2019-both-be-installed) it was stated, that this issue was escalated to product management to be considered for PB2019 R2, but no news on it since.

Can you offer any new information on this issue? Will it be fixed in PB2019 R2?

Thank you in advance!


Julie Jiang @Appeon Accepted Answer Pending Moderation
  1. Thursday, 21 November 2019 00:44 AM UTC
  2. PowerBuilder
  3. # 1

Hi Marc/Michael, 

Sorry for this inconvenience.  Because of the tight schedule, we cannot address this issue yet in the coming 2019R2. However, we do have plan to change the behavior in 2019R3, to allow you to log in to multiple major versions simultaneously on the same machine. 

Best regards, Julie

There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Wednesday, 20 November 2019 15:31 PM UTC
  2. PowerBuilder
  3. # 2

Same license counting behavior in PB2019 R2 as in PB 2019 GA - and no whisper through the grapevine that changes are expected by R2 release.

  1. Marc Wietscher
  2. Wednesday, 20 November 2019 16:06 PM UTC
Hi Michael,

thanks for your reply.

For us this means we are stuck to PB2017. So we will pay year by year to work with the same PB release until we move away from PB completly. And even after that we have to continue paying our licences annually to maintain our by then obsolete PB applications.

To me, this approach does not seem fair. We paid for a software (and still do and will continue to do) but we are not able to use it, unless we stop using another software (actually the same software but different version), that we also paid for.

Why does licence counting work fine when starting PB2017 several times? What's the difference? Not technically, but legally. It does not make any sense to me.

Best regards

  1. Helpful
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.