Code compatibility of PowerBuilder 8 to PowerBuilder 11

[Jigar Prajapati]

Hi,
We have application developed in PB8 and now we are planning to migrate with PB 11. what will the compatibility of the code with version 11. do we need to change any code in that?

[Jason Fenter]

The Transport object was dropped in PB9. If you have any references to that (the PFC does), then you'll need to remove that code. With PB10, PowerBuilder became Unicode-compliant. You'll have to review all of your external function calls to see which ones need to be switched from the ANSI version (i.e. GetModuleFileNameA) to the Unicode version (i.e. GetModuleFileNameW). The migration assistant within PowerBuilder will help with this, but it marks all of your external functions with an ANSI option (GetModuleFileNameA;ANSI). And finally, the PFC has a hard-coded reference to an external function in PBVM80.dll. Later versions moved this function call to pure PowerScript. If you use the PFC, you might want to download the latest version from CodeXchange instead of migrating your current PFC libraries.

Terry Voth has a good migration guide on his website.

[Sanjeet]

I have recently migrated PB5 to PB11. I havent done any code changes, migration prity much handles all coding.

[Jeff Wayt]

If you are using PFC, read on.

Migrate the code you have.
Create a custom veneer library for any PFE objects at the top of your library list before the PFE/PFC libs.
Substitute Just the PFC libraries first, then do a full build.
Follow with PFE after resolving any issues, if you want.
Resync PB extensions in the database if you want.

I have migrated PB 7 to 11.5

NOTE! PB 11.2 is the last version that works on Windows 2000. PB 11.5 will not.