The following is a list of key unsupported features to consider before migrating to 64-bit architecture: (read more)
-
Web Services Client (Discontinued)
Creating Web service proxy for connecting to SOAP server is a discontinued feature. Additionally there is no 64-bit version of the client. So, you must use the PowerBuilder HTTPClient Object instead. You can follow these instructions: Call SOAP Web Services using HTTPClient Object in order to successfully replace the Web Services Client before migrating your application to 64-bits.
-
COM+ runtime (read more)
Building a COM+ client in 64-bit is currently not supported.
-
Machine code generation
Generating PowerBuilder machine code DLLs is not supported for 64-bit applications. But you can still opt for compiling as P-code which is supported (read more).
This feature is tentatively planned for PowerBuilder 2022.
-
TabletPC
These TabletPC features are not supported on 64-bit applications:
Currently there are no substitute for these features.
-
PBNI SDK
Currently there is no 64-bit version of the PBNI SDK.
-
Application server support (read more)
PowerBuilder developers can build clients that invoke the services of COM+ and third-party application servers, and build components (or objects) that execute business logic inside each of these servers.
Currently it is not supported to create 64-bit components for application servers with the PowerBuilder IDE. However, you can use the SnapDevelop IDE (bundled with PowerBuilder) to create 64-bit components in C# with DataWindow technology.
