After an application has been upgraded to PowerBuilder 9.0, 10.0, or 10.5, some DataWindows or DataWindow columns may not be saved in the correct PowerBuilder 9.0, 10.0, or 10.5 formats. This issue seems to most often affect applications upgraded from PowerBuilder 5.0 or 6.0.
For the Appeon Xcelerator deployment option, the Appeon Developer Feature Analysis tool can catch DataWindows that are not correctly upgraded. For the Pure-JavaScript deployment option, the Feature Analysis tool cannot catch such DataWindows.
The older PowerBuilder format will cause one of two errors that are documented below with solutions:
Error #1 - in the application deployment, the task 1 "application source code export" exits abnormally while trying to get the list of objects from application PBLs.
Solution - open each DataWindow of the application in PowerBuilder 9.0, and save the DataWindow again using the same DataWindow name.
Error #2 - some DataWindow columns do not display any data.
Solution - open the affected DataWindow in PowerBuilder 9.0, change the DataWindow column to another name and save. Then change the column back to the original name and save again.
