1. John Mitrik
  2. PowerBuilder
  3. Tuesday, 22 February 2022 22:44 PM UTC

 

 

Hello all!

 

I am working on a PowerBuilder application for my company and we're trying to upgrade it to the latest version. We currently use PB 9.5 and I was going to begin my conversion from there, however,  I just learned from another developer at my company that we have a majority of our app upgraded to PB version 12.5 already, but that we are missing a runtime DLL that supports datawindows.

He said to me in an email “The only thing left was to find the missing DLL that is needed for the datawindows to work correctly at runtime.”

The thing is he’s not 100% which dll it is because he last attempted this 2-3 years ago.


I found an old Sybase wiki and found that it may be pbdwe125.dll and while I’m 99% sure that’s the one we are missing, could anyone be able to either supply to me pbdwe125.dll, or, possibly even better, all of the 12.5 runtime files so that we can start our upgrade process from 12.5 rather than from 9.5?

 (https://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc37774.1250/html/apptech/BGBEBIEA.htm)

I also wonder for anyone who has done migrations before, is there is a good chunk of work saved by upgrading from 12.5 to 2021 vs upgrading from 9.5 to 2021?

 

Thanks!

 

(edit: grammar)

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 24 February 2022 17:57 PM UTC
  2. PowerBuilder
  3. # Permalink
Hi John; Going to a supported version of Appeon PB might be a better approach at this point considering how fragmented your PB Apps are PB runtime (aka DLL uncertainty) wise. If you decide to go to PB2019/2021, I would highly recommend using the "Migration Wizard" in the Appeon PB IDE first. Run this utility on your PB 12.5 / PB9 code App libraries first before any migration takes place. Just to make sure that if it points out any ANSI PowerScript or External API declarations inconsistencies that you might need to address for the actual migration process to be successful. Regards ... Chris
Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 22 February 2022 23:57 PM UTC
  2. PowerBuilder
  3. # 1

Hi John;

  You have to be careful as there was a 12.5, 12.5.1 & 12.5.2 release I the 12.5x series of PB releases and yet all the runtime DLLs were named PBxxx125.dll.

Regards ... Chris

 

 

Comment
  1. John Mitrik
  2. Wednesday, 23 February 2022 17:30 PM UTC
Thanks Chris,



I am wondering now, and please excuse me for my ignorance -- since we last attempted the upgrade to 12.5 we have had about 5 pbls that receive regular updates -- to upgrade to 2021 would I be able to include the large amount of 12.5-updated pbls and the few 9.5 pbls in the same project and then use the upgrade tool that is built in, or would I have to get all pbls to the same version before trying to upgrade? It seems I can't escape the ANSI/Unicode conversion for a few pbls but 5 somehow feels more manageable than 102
  1. Helpful
  1. mike S
  2. Wednesday, 23 February 2022 19:47 PM UTC
" few pbls but 5 somehow feels more manageable "



I agree with chris that going to PB2019/2021 would be a better approach. Make sure you have backups before migration.



I would first try to migrate all but those 5 trouble pbls. For those 5, you can export your source code, then import that source code into your PB2021 versioned pbls. I use this technique a lot.
  1. Helpful 1
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Wednesday, 23 February 2022 16:12 PM UTC
  2. PowerBuilder
  3. # 2

John -

   I have the DLLs for the 12.5 series. Which version do you need - this means the version & build number.

   Here's what I have:



Later -

Olan

Comment
  1. John Mitrik
  2. Wednesday, 23 February 2022 17:30 PM UTC
Olan, as per the reply I got from Chris, and based on everything I'm seeing, I think I need just the 12.5 release.



Hi John;



You have to be careful as there was a 12.5, 12.5.1 & 12.5.2 release I the 12.5x series of PB releases and yet all the runtime DLLs were named PBxxx125.dll.



Regards ... Chris















  1. Helpful
  1. Olan Knight
  2. Wednesday, 23 February 2022 17:46 PM UTC
Give me a URL that I can FTP the installer to you, please.
  1. Helpful
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 22 February 2022 23:08 PM UTC
  2. PowerBuilder
  3. # 3

Hi, John - 

I'm sorry that I do not have PB 12.5.2 installed, but I'm confident that someone in the Community will be able to help you with that.

Yes, you will NOT have to concern yourself with the ANSI -> Unicode conversion that occurred when PB 10 was released. PB changed internally from single-byte ANSI to Unicode 16LE (two bytes/character), and that was a relatively major change.

Good luck!

Comment
There are no comments made yet.
Brad Mettee Accepted Answer Pending Moderation
  1. Wednesday, 23 February 2022 14:15 PM UTC
  2. PowerBuilder
  3. # 4

I'm a bit confused here.

If you have an app that's already been upgraded to 12.5.x, how is it that the developer that compiled it doesn't have the DLLs for it? 

Comment
  1. John Mitrik
  2. Wednesday, 23 February 2022 15:43 PM UTC
It's a runtime DLL, afaik it's a file that doesn't prevent the use of the PB dev environment, but that doesn't allow the built version of the app to access datawindows -- so I guess I should say we have a partially untested upgrade to 12.5 (I would imagine some issues will crop up once we can actually run the portions that have datawindows .



I believe this happened because there was a bug in a download from either Sybase or SAP that was missing this DLL
  1. Helpful
  1. mike S
  2. Wednesday, 23 February 2022 15:55 PM UTC
If you have source that is upgraded to 12.5 and you are trying to upgrade that to 2019 or 2021, then why do you want a runtime dll for 12.5x?
  1. Helpful
  1. Brad Mettee
  2. Wednesday, 23 February 2022 16:04 PM UTC
The point I was making is that if the developer can run the application from the IDE, then the DLLs are all present on his system already.



If you're having problems accessing datawindows at runtime, maybe it's because they were dynamically assigned and aren't built in to the EXE. Are you using PBD's or a PBR to force them to be included?
  1. Helpful
There are no comments made yet.
Shenn Sellers Accepted Answer Pending Moderation
  1. Wednesday, 23 February 2022 16:03 PM UTC
  2. PowerBuilder
  3. # 5
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.