Migration to PowerBuilder Classic

You can migrate applications from any earlier version of PowerBuilder to PowerBuilder Classic 12.5.

Before you migrate, back up your files and use the Migration Assistant to identify obsolete code. The applications you build using the current version of PowerBuilder must be deployed with the PowerBuilder runtime DLLs from the current version.

• Migrating .NET Targets from Earlier Versions of PowerBuilder
  When you migrate older Web Forms applications and .NET Web Service components, you might need to remove or install supporting files on development and deployment computers.
• Migrating EAServer Targets
  Migratiing EAServer targets from earlier versions of PowerBuilder to PowerBuilder Classic may require some additional considerations. PowerBuilder .NET does not support EAServer targets.
• System Types as Variable Names in Proxies
  In PowerBuilder versions 10.5 and later, system types cannot be used as variable names in Web service proxies.
• OLE DB Performance with Microsoft SQL Server
  In PowerBuilder 10.5.2 and later, when you use the OLE DB database interface with a Microsoft SQL Server database and retrieve data into a DataWindow, or use an embedded SQL cursor in a SELECT statement, server-side cursors help to support multiple command execution.
• Change in Behavior of OpenTab
  A change was made in PowerBuilder 10.2.1 Build 9716, PowerBuilder 10.5.1 Build 6505, and PowerBuilder 11.0 Build 5021, to correct an anomalous behavior when the SelectedTab property was applied at runtime to a tab for which the Visible property was set to false.
• ImportFile Size Limit
  If your application uses the ImportFile method to import very large text files into a DataWindow or DataStore, ImportFile returns the error code -15.