Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Conversion of powerbuilder 2022 from 32-bit to 64-bit version

  1. Advice
0
Votes
Undo
  1. Praveen Subramaniam
    Praveen Subramaniam
  2. PowerBuilder
  3. Friday, 30 August 2024 04:11 AM UTC

Currently we are using PowerBuilder application developed using power builder 2022 32-bit version. Since business want to move to windows 11 machine which supports only 64-bit versions. 
We need input and confirmation on converting 32-bit PowerBuilder application to 64-bit version and steps to convert that.

  1. 32-bit
  2. 64-bit
  3. Versioning
Icon File in PNG format
Issue with ODBC to OLE DB Connection
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 30 August 2024 12:05 PM UTC
  2. PowerBuilder
  3. # 1

Hi Praveen;

  FYI ... Your management is misinformed as W11 supports both 32 & 64 bit Apps.

  In the meantime though, check John's document link.

Regards ... Chris 

Comment
Francisco Martinez @Appeon
  1. Francisco Martinez @Appeon
  2. Friday, 30 August 2024 15:34 PM UTC
I agree, I think there's a misunderstanding on their management side. While it is true that W11 will only provide a 64-bit OS version, that doesn't mean 32 bit apps won't be supported (that would be a compatibility nightmare, and Microsoft prides themselves on being very backwards-compatible). Most 64bit OSs generally support 32bit apps out of the box and W11 is not the exception. So if the reason they want to take on such an endeavor such as migrating to x64 only because of this misunderstanding there's no need to go through the pain.
  1. Helpful 2
There are no comments made yet.
Luc Railhac
Luc Railhac Accepted Answer Pending Moderation
  1. Friday, 30 August 2024 06:32 AM UTC
  2. PowerBuilder
  3. # 2

The Appeon publication provided by John is worth reading but may seem a bit intimidating.

FYI this year we migrated a large PB application from 32 to 64 bits and everything was fine on first run without any change to our code, except one thing that was discovered later in QA: the print jobs did not work anymore.

The reason is simple and explained in the help file, the return value of the PrintOpen() function is a long in 32 bits and longlong in 64, so we only had to make this change.

Your experience may differ but at least you'll have the answer to this specific issue.

Regards,
Luc

 

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 30 August 2024 15:07 PM UTC
We are reluctant to migrate to 64 bit just because of this. There's no compilation errors / warnings if you don't declare an external function correctly. I would be great if someone (Appeon ?) could make a list of the most used external win api functions and give us the correct definition. John's stuff is great but not all inclusive. "Handles" have to be longptr, but what if they're not named as handle-something? Just an example. What about structs that we have to modify? Honestly, Appeon would do us a GREAT favour by showing us warnings while compiling our pb code.

Just begging :)
  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 2 September 2024 15:22 PM UTC
Yes, it's a QA nightmare. But you can target the external functions in the system as you know these may be a problem.
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Friday, 30 August 2024 05:31 AM UTC
  2. PowerBuilder
  3. # 3

Hi, Praveen - 

I suggest you start by reading the following Appeon publication carefully and thoroughly:

    https://docs.appeon.com/pb2022r3/migrating_32bit_applications_to_64bit/index.html

Does your application utilize Windows API calls or external function calls to third-party DLL's? The above document discusses this also.

Please follow up here if you have additional questions on this topic.

Best regards, John

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.