HomeAppeon Web | Appeon Mobile | Appeon PowerBuilderAppeon Online Help Center

Functions for DataWindowChild

Supported

There are some limitations or differences for calling functions marked with the "*" symbol. Refer to the Limitations and Differences for Calling Functions.

Table 284. 

AcceptText

ClassName

DeletedCount

DeleteRow

Describe

Filter

FilteredCount

Find

FindGroupChange

FindRequired

GetBandAtPointer

GetBorderStyle

GetChanges

GetChild

GetClickedColumn

GetClickedRow

GetColumn

GetColumnName

GetFormat

GetItemDate

GetItemDateTime

GetItemDecimal

GetItemNumber

GetItemStatus

GetItemString

GetItemTime

GetNextModified

GetObjectAtPointer

GetParent

GetRow

GetSelectedRow

GetSQLPreview

GetSQLSelect*

GetText

GetValidate

GetValue

GroupCalc

ImportClipboard*

ImportFile*

ImportString*

InsertRow

IsSelected

ModifiedCount

Modify*

Reset

ResetUpdate

Retrieve

RowCount

RowsCopy

RowsDiscard

RowsMove

SaveAs*

ScrollNextPage

ScrollNextRow

ScrollPriorPage

ScrollPriorRow

ScrollToRow

SetChanges

SetColumn

SetFilter

SetDetailHeight

SetFormat

SetItem

SetItemStatus

SetPosition*

SetRedraw

SetRow

SetRowFocusIndicator

SetSort*

SetSQLPreview

SetSQLSelect

SetTabOrder

SetText

SetTransObject

SetValue

SetValidate

SetWSObject*

ShareData

SharedDataOff

Sort*

TypeOf

Update

    

Unsupported

Table 285. 

CrosstabDialog

DBCancel

DBErrorCode

DBErrorMessage

ExportJson

GetContextService

GetRowIDFromRow

GetRowFromRowID

GetTrans

GetUpdateStatus

ImportJson

ImportJsonByKey

OLEActivate

ReselectRow

ResetTransObject

SaveNativePDFToBlob

SelectRow

SetBorderStyle

SetTrans

Limitations and Differences for Calling Functions

  • GetValue

    The column argument does not work only if the edit style of the column is CheckBox, DropDownListBox, Edit, or RadioButton.

  • GetSQLSelect

    If the syntax in DataWindow is PBSELECT statement, when calling the GetSQLSelect function, it will still return the PBSELECT statement but not the SQL SELECT statement, which is different from that in PowerBuilder.

  • ImportFile, ImportString, ImportClipboard

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

    2. The string argument of ImportString function must be a tab-separated string (text).

    3. 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.

    4. When using the three 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).

  • Modify

    If the Modify function is used to modify the WHERE clause of the DataWindow object's SQL SELECT statement, please make sure that the new SQL SELECT statement is correct in syntax. Otherwise, syntax errors can occur because PowerBuilder does not validate the statement whereas JavaScript does.

    When executing Modify function to change the dddw.property on the Web, properties must be separated with spaces when they are concatenated into one value. For example,

    Unsupported code:

    dw_1.Modify = "emp_id.BackGround.Color=" + String(RGB(192,192,192)) + "emp_id.Protect=1"

    Supported code:

    dw_1.Modify = "emp_id.BackGround.Color=" + String(RGB(192,192,192)) + " emp_id.Protect=1"

    In PowerServer Web, the Modify function cannot be used to modify the database information.

  • SaveAs

    1. The 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.

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

    3. The supported SaveAs syntax:

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

      SaveAs PDF cannot support the colheading argument, for example, the following syntax is unsupported: 

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

      The unsupported SaveAs syntax:

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

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

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

  • SetSort

    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.

  • SetPosition

    The following syntax is supported:

    dwcontrol.SetPosition (position{, precedingobject})

    The position can be ToTop!, ToBottom!, but cannot be Behind!

    The following syntax is unsupported:

    dwcontrol.SetPosition(objectname, band, bringtofront)

  • SetWSObject

    The SetWSObject function is used to set the authentication info for accessing Web service.

  • Sort

    If the items in a Web DropDownDataWindow are double-byte (such as, Chinese, Korean, or Japanese), sorting the DropDownDataWindow has a different result from PowerBuilder. This is because the sorting method of PowerScript and JavaScript is different. For example, if the charset is Chinese, PowerScript sorts by the spelling while JavaScript sorts by Unicode.

Prev  Up  Next
Properties of DataWindowChild object  Home  DataWindow performance considerations