In a PowerBuilder application, if the user saves a file (such as a text file) to a folder other than the PowerBuilder application folder, the relative path of the PowerBuilder application is changed to the specified path. As a result, the images in the PowerBuilder application cannot be retrieved successfully from the correct relative path and displayed in the application.
This is normal behavior for PowerBuilder. As a workaround, always save these files to the PowerBuilder application folder.
Appeon applies PowerBuilder SaveAs for generating readonly DataWindows. If the data for the readonly DataWindow is too large (more than 10 thousand rows), PowerBuilder SaveAs cannot save the data into WMF file, and the readonly DataWindow only displays blank page.
Workaround #1 - enable Appeon DataWindow Menu for the DataWindow. In the Web application, the user can view the DataWindow in PDF format via the Appeon DataWindow Menu Print View item. Refer to the Web Enhancements and Differences section in Appeon Features Help for instructions on how to enable Appeon DataWindow Menu.
Workaround #2 - reduce the number of rows in the DataWindow to avoid the problem.
Nested reports longer than five pages cannot be viewed in the DataWindow of the Web application. This is caused by a limitation of PowerBuilder.
Workaround - enable the server-side PDF printing for the DataWindow. In the Web application, the user can view the DataWindow in PDF format. Refer to the DataWindow printing section in Appeon Features Help for Appeon Xcelerator for instructions on how to enable server PDF printing.
A nested report runs in a client/server application
but cannot be opened on the Web and an error dialog box similar
to Expecting 3 retrieval arguments but got 1 or Nested
arguments are incorrectly specified appears.
Possible solution - in the PowerBuilder application, open the report and move it one unit to one side and then back to its original position. Redeploy the application using the deployment wizard.
If a composite DataWindow contains an editable DropDownDataWindow column, the DropDownDataWindow column may display in its actual value instead of displaying a value due to a PowerBuilder SaveAs bug (CR 367968).
Workaround - enable server-side PDF printing for the DataWindow. In the Web application, the user can view the DataWindow in PDF format. Refer to the DataWindow printing section in Appeon Features Help for Appeon Xcelerator for instructions on how to enable server PDF printing.
