When you deploy a PowerBuilder application as a Web Forms application to an IIS server, PowerBuilder lists any unsupported features in the Output window. For the most part, unsupported features fail silently in the Web Forms application, but unexpected results can also occur. If an unsupported feature prevents the PowerBuilder to .NET compiler from compiling your application, the failure and its cause are noted in the Output window in PowerBuilder.
Presentation styles Currently all DataWindow presentation styles are supported except RichText and OLE. All DataWindow dialog boxes (Specify Retrieval Arguments, Specify Retrieval Criteria, Import File, Save As, Print, Sort, Filter, and Crosstab) are supported.
DataWindow expressions Most of the built-in functions for DataWindow expressions are supported, but they do not include the Describe, LookupDisplay, Case, Page, PageAbs, ProfileInt, and ProfileString expression functions or the aggregate expression functions. User-defined expression functions are also not supported in Web Forms applications.
Client-side DataWindow expressions
DataWindow expressions that change UI properties are not supported
on the client side. To work around this issue, you can trigger the
Clicked or RowFocusChanged event to force a postback. DataWindow
expressions are fully supported on the server side with the exception
of expression functions noted above.
Controls in DataWindow controls The controls you can add to a DataWindow are not all supported in Web Forms applications. The Oval, RoundRectangle, InkPicture, OLE Object, and OLE Database Blob controls are not supported in a Web Forms DataWindow. For a list of unsupported properties of controls that are supported in Web Forms DataWindow objects, see Table 8-5.
JavaScript keywords You cannot use JavaScript reserved words to name fields or bands in a DataWindow control that you deploy to the Web. The list of reserved words is available on the Sun Microsystems Web site.
DataWindow pagination The Web DataWindow control uses a simplified version of DataWindow pagination rules, and provides a choice of page navigation bars instead of scroll bars to support page navigation.
For information on pagination display in Web Forms DataWindow controls, see “Take advantage of global configuration properties”. For a description of changes to the visual display of DataWindow controls in Web Forms applications, see “Modified display of DataWindow objects and controls”.
Printing DataWindow objects Although the PrintDataWindow or PrintScreen print functions are not supported, users can save DataWindow objects and their data as PDF files, and can print the current Web Forms page using a browser’s print menu when those are available. (Browser menus are available only when the default.aspx page name is included in the URL used to start the Web Forms application.)
Although you can send e-mail from Web Forms applications, there is no support for receiving e-mail. When you call MailSend, you must supply a MailMessage argument. The MailSend syntax without a parameter is not supported.
The MailSend function returns an enumerated value of type MailReturnCode. The following values of the MailReturnCode enumeration are not supported in Web Forms applications:
MailReturnAccessDenied |
MailReturnNoMessages |
MailReturnDiskFull |
MailReturnTextTooLarge |
MailReturnInsufficientMemory |
MailReturnTooManyFiles |
MailReturnInvalidMessage |
MailReturnTooManyRecipients |
MailReturnMessageInUse |
MailReturnTooManySessions |
You cannot use PBNI extensions in .NET Web Forms targets.
Hot keys, shortcut keys, and accelerator keys are not supported in .NET Web Forms targets.
You cannot call functions on .NET primitive types that map to PowerBuilder primitive types. See Table 13-3 for the list of datatype mappings from .NET to PowerBuilder.
