Have you gone through the 64-bit migration guide?  https://docs.appeon.com/pb2022r3/migrating_32bit_applications_to_64bit/index.html

Do you have any 32-bit DLLs/OCXs?

Did you adjust any Win API calls?

I did go through the 64-bit migration guide. I was able to compile all external dll's as 64-bit. I have not made any Win API adjustments, I am not sure if I need to or not. 

Hi Mike;

  Does your PB App work correctly when run in 64 bit mode from the PB 2022 R2 IDE?

  If the 64 bit App runs OK under the IDE, then make sure that you deploy the 64 bit PB runtime via the "PB Packager" utility and also include the generated <AppName>.XML file with your  PB App' EXE in the same deployment folder. Note that you might need to edit that XML file for the proper PB runtime location on the deployment machine.
Regards .. Chris

Hi Chris,

The application does run in the IDE with the x64 option selected and the xml file points to the correct runtime files folder.

Mike

The Event Viewer info says that pb220.exe aborted. Am I right that the PowerBuilder IDE is aborting while you are deploying to 64bit? The questions/answers you've gotten so far talk about your application aborting.

Yes, PB2022R2 is crashing when trying to deploy the application. The application runs with the x64 option selected and a manual full build completes without error.

I tried to deploy using the command prompt option pbc220.exe with the PBC runtime parameters generated by the build object in the PB2022R2 IDE. The completes with errors but the errors are information errors, i wouldn't think that would cause the process to crash, also I can see "Rebuild complete" before the errors...

Library: c:\users\mkochevar\tfs2016\boston\pims\release22.0.0.0\flxsb\flxsb.pbl Object: uo_flxsb_container Function: uo_flxsb_container::move
(0001): Information C0148: The identifier 'x' conflicts with an existing property with this name. The new definition of 'x' will take precedence and the prior value will be ignored until this version of 'x' goes out of scope.
(0001): Information C0148: The identifier 'y' conflicts with an existing property with this name. The new definition of 'y' will take precedence and the prior value will be ignored until this version of 'y' goes out of scope.
Library: c:\users\mkochevar\tfs2016\boston\pims\release22.0.0.0\pims_base\pims_base.pbl Object: w_browser ole_browser Class Declaration
(0009): Information C0148: The identifier 'cancel' conflicts with an existing property with this name. The new definition of 'cancel' will take precedence and the prior value will be ignored until this version of 'cancel' goes out of scope.
(0010): Information C0148: The identifier 'cancel' conflicts with an existing property with this name. The new definition of 'cancel' will take precedence and the prior value will be ignored until this version of 'cancel' goes out of scope.
(0020): Information C0149: The identifier 'resizable' conflicts with an existing property with this name in the parent class. The new definition of 'resizable' will take precedence and the prior value will be ignored until this version of 'resizable' goes out of scope.
(0025): Information C0148: The identifier 'cancel' conflicts with an existing property with this name. The new definition of 'cancel' will take precedence and the prior value will be ignored until this version of 'cancel' goes out of scope.
(0028): Information C0148: The identifier 'cancel' conflicts with an existing property with this name. The new definition of 'cancel' will take precedence and the prior value will be ignored until this version of 'cancel' goes out of scope.
(0029): Information C0148: The identifier 'cancel' conflicts with an existing property with this name. The new definition of 'cancel' will take precedence and the prior value will be ignored until this version of 'cancel' goes out of scope.
Library: c:\users\mkochevar\tfs2016\boston\pims\release22.0.0.0\pfeapsrv\pfeapsrv.pbl Object: w_logon Object Variable Declarations
(0001): Information C0146: The identifier 'w_logon' conflicts with an existing global variable with this name. The new definition of 'w_logon' will take precedence and the prior value will be ignored until this version of 'w_logon' goes out of scope.
Library: c:\users\mkochevar\tfs2016\boston\pims\release22.0.0.0\pims_ad_hoc_query\sqlbuilder\sqlbuilderprosourcecode\pb90\sqlbuilderdemo80.pbl Object: w_logon Object Variable Declarations
(0001): Information C0146: The identifier 'w_logon' conflicts with an existing global variable with this name. The new definition of 'w_logon' will take precedence and the prior value will be ignored until this version of 'w_logon' goes out of scope.
Library: c:\users\mkochevar\tfs2016\boston\pims\release22.0.0.0\flxapi\flxapi.pbl Object: nv_flxapi_tooltip Function: nv_flxapi_tooltip::of_relaymsg
(0016): Information C0146: The identifier 'msg' conflicts with an existing global variable with this name. The new definition of 'msg' will take precedence and the prior value will be ignored until this version of 'msg' goes out of scope.

Hi John,

I have attached the WinAPI calls from a third party dll call flx suite. There are many other WinAPI calls in the application but I thought I would start small. The dll is written in powerbuilder, I am surprised it works in 32-bit as it also calls PVBM###.dll depending on the version of PB being used, the latest version was a call to PBVM110.dll.

Thank you for your time,

Mike

I've taken a look at the Félix Informatique web site and it appears that they have not updated their product since PB v11, and I'm guessing they have no plans to do so and no longer support their product.

I've also taken a look at the "easy" list of external function declarations you attached. There are roughly 115 external function declarations to API functions in seven different Windows system DLL's. Many can be updated as Roland described, by changing the datatype for handles and memory addresses from Long/ULong to Longptr... but some may be more challenging to migrate, particularly those where structures are involved.

There are many external function declarations where ANSI/Unicode translation is being performed. Presumably this is because Flx Suite was created when PB did not yet have Unicode support, so the developer(s) continued passing ANSI-encoded data when the suite was migrated to PB 10. The translation of character/string arguments to/from ANSI/Unicode works well, but the translation adds needless overhead.

If it were me, I would migrate the app and Flx suite to PB 2022 as a 32-bit app first that passes Unicode, test it thoroughly, get familiar with the packaging and runtime requirements of apps in PB 2022. Next, make the Longptr datatype changes, but continue generating a 32-bit app and get that working well. Then finally, tackle the conversion to 64-bit, but only if it is necessary. In my view, there is nothing wrong with having a 32-bit application, especially since you have so many Windows API external functions that will need to be examined and probably modified. Remember, it's not just the declarations that have to change, but the datatypes of the variables that are passed as arguments and the code that manipulates those variables.

I wish you well with your project. Remember we're here to help answer questions.

Hi Chris,

I am not sure how to answer your question about deploy vs creating an exe. The build project I use creates the exe and when I deploy to another PC I copy the new exe and all of the .pbd files to the PC and run the exe. The PB IDE crashes when the project is in the deploy process. I have attached a screenshot of the build projects General tab and the button I am clicking on to start the process.

Thank you for your time,

Mike