Also, PBD files are not bitness specific. Only the EXE is 32 or 64 bit. If you use pbx2pbd220 to create a PBD file, you only need to do it once in 32-bit. You can use the same PBD in both 32 and 64 bit versions of the EXE.

I just use the 'Import PB Extension' option to import the interface objects into a PBL within the target. I find it much easier that way. The PBX only has to be imported once. You might be able to import the 64-bit version of the PBX if the IDE is in 64-bit mode, I haven't tried it. I always compile both and use the 32-bit version in the IDE. I then test the 64-bit version with the executable.

Hi Kari,

Please refer to this documentation:
https://docs.appeon.com/pb2022r3/migrating_32bit_applications_to_64bit/header-n166.html

Since PowerBuilder IDE is 32-bit, this introduces some challenges with PBNI interfacing with 64-bit. In the PowerBuilder IDE, you can only import the 32-bit PowerBuilder extensions into the PBL (using the Import PB Extension context menu) or create the PBD file from the 32-bit PBX file using the pbx2pbd220.exe tool. But for runtime, you can still package and distribute the 64-bit extension libraries with your 64-bit applications. What you need to do is compile the extension libraries to 64-bit PBX files using the Visual Studio Wizards, and make sure your 64-bit PBX files have the same name as the 32-bit files, since the application references it by file name.

Regards,
Ken