Supported PB Features for PowerServer Web
DataWindow control

The filename argument of ImportFile function must be a tab-separated file (TXT) or a comma-separated file (CSV).

The importtype arguments (e.g. Text!, CSV! and XML!) of ImportString function are unsupported.

The importtype arguments (e.g. Text!, CSV!, XML!, DBase2!, DBase3!) of ImportFile function are unsupported.

When using these functions, you should ensure that the data type imported matches the data type that you specified in a DataWindow control, DataStore object or graph control. Otherwise the output on the Web may be different from that in PowerBuilder. For example, if the date type specified in a DataWindow is string, when you import a file with date number (e.g., 2006-08-01), on the Web the date data will be recognized as a string (2006), however in PowerBuilder, it will be recognized as a date data (2006-08-01).

Arguments specified in the Print function will be ignored in a Web application. Even if theCancelDialog argument is set to TRUE or FALSE, no Cancel dialog will be displayed on the Web to cancel printing.

When the Print function is executed for a DataWindow that contains a Text control with BorderType as None and actual length of the content larger than the length of the control, the printing result shows the content in the Text control the same way as the control is displayed in the application, although in PowerBuilder, the printing result shows the full content in the Text control.

For controls, print function is only supported when called in Graph controls with the following syntax.

integer objectname.print (long printjobnumber, integer x, integer y{, integer width, integer height})

On the Web, Nillable attribute is unsupported in an XML schema.

The supported SaveAs syntax :

ll_testvalue = dw_test.SaveAs(filename, saveastype, colheading, encoding)

In the syntax:

The value of a saveastype argument can be TEXT, HTMLTable, XML, PDF*, EXCEL, or EXCEL5. For the EXCEL format, only up to 256 characters are supported and anything larger will be automatically truncated.

When saveastype is PDF, the colheading argument is unsupported, for example, the following syntax is unsupported:

Integer dwcontrol.SaveAs({string filename, saveastype saveastype, boolean colheading{, encoding encoding}})

The unsupported SaveAs syntax:

dw_test.SaveAs([filename, ]graphcontrol[, saveastype, colheading])

If the DataWindow without any data is saved as an HTML file or XML file, on Web the DataWindow header will not be saved, whereas it will be saved on PB.

The generated file is automatically saved to the "plugin" folder under the current application directory. See "plugin" folder in Workarounds & APIs Guide for more.

If the Format argument of the SetSort contains sorting criteria for more than one column, the criteria of the columns must be separated with commas.

Using desc or asc as the Order will not have any effect. Please use the standard Order value A for ascending or D for descending order.

Because PowerServer Web applications cannot check whether the retrieve result set matches the DataWindow definition syntax, the DBError event will not be triggered.

Supported:

CONNECT USING SQLCA;
dw_corp.SetTransObject(SQLCA)
dw_corp.Retrieve()
dw_corp.ShareData(dw_emp)
dw_corp.ShareData(dw_dept)
... // Some processing
dw_emp.ShareDataOff()

In Web applications, if any data in two data-sharing Group DataWindows are changed, the primary Group DataWindow will be re-grouped and re-sorted automatically, while the secondary Group DataWindow will only be re-grouped.

The row and column status is shared between the primary DataWindow and secondary DataWindow on the Web, although not shared in PowerBuilder.