DataStore Object

Table 217. Events

Support Level

Feature Name

Description

Supported

Constructor

 

Supported

DBError

 

Supported

Destructor

If a non-visual object is a local variable, the Destructor event in the non-visual object cannot be triggered unless there is a Destroy statement for the non-visual object as well.

Unsupported

Error

 

Supported

ItemChanged

 

Supported

ItemError

 

Unsupported

PrintEnd

 

Unsupported

PrintPage

 

Unsupported

PrintStart

 

Supported

RetrieveEnd

 

Unsupported

RetrieveRow

 

Supported

RetrieveStart

 

Supported

SQLPreview

The SQLPreview event can be triggered by Retrieve method, but cannot be triggered by the Update or ReselectRow methods.

Supported

UpdateEnd

 

Supported

UpdateStart

 

Supported

WSError

 


Table 218. Functions

Support Level

Feature Name

Description

Supported

AcceptText

 

Unsupported

CategoryCount

 

Unsupported

CategoryName

 

Supported

ClassName

 

Supported

ClearValues

 

Unsupported

Clipboard

 

Unsupported

CopyRTF

 

Supported

Create

 

Unsupported

CreateFrom

 

Unsupported

DataCount

 

Unsupported

DBCancel

 

Supported

DeletedCount

 

Supported

DeleteRow

 

Supported

Describe

 

Supported

Filter

 

Supported

FilteredCount

 

Supported

Find

 

Unsupported

FindCategory

 

Supported

FindGroupChange

 

Supported

FindRequired

 

Unsupported

FindSeries

 

Supported

GenerateHTMLForm

 

Unsupported

GenerateResultSet

 

Unsupported

GetBorderStyle

 

Supported

GetChanges

 

Supported

GetChild

 

Unsupported

GetClickedColumn

 

Unsupported

GetClickedRow

 

Supported

GetColumn

 

Supported

GetColumnName

 

Unsupported

GetContextService

 

Unsupported

GetData

 

Unsupported

GetDataPieExplode

 

Unsupported

GetDataStyle

 

Unsupported

GetDataValue

 

Supported

GetFormat

 

Supported

GetFullState

 

Supported

GetItemDate

 

Supported

GetItemDateTime

 

Supported

GetItemDecimal

 

Supported

GetItemNumber

 

Supported

GetItemStatus

 

Supported

GetItemString

 

Supported

GetItemTime

 

Supported

GetNextModified

 

Supported

GetParent

 

Supported

GetRow

 

Supported

GetRowFromRowId

 

Supported

GetRowIdFromRow

 

Supported

GetSelectedRow

 

Unsupported

GetSeriesStyle

 

Supported

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.

Unsupported

GetStateStatus

 

Supported

GetText

 

Unsupported

GetTrans

 

Supported

GetValidate

 

Supported

GetValue

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

Supported

GroupCalc

 

Unsupported

ImportClipboard

 

Supported

ImportFile

ImportFile & ImportString

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

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

  3. 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 mobile 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 mobile the date data will be recognized as a string (2006), however in PowerBuilder, it will be recognized as a date data (2006-08-01).

Supported

ImportString

Please see the notes for ImportFile.

Unsupported

InsertDocument

 

Supported

InsertRow

 

Supported

IsSelected

 

Supported

ModifiedCount

 

Supported

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 on mobile because PowerBuilder does not validate the statement whereas JavaScript does.

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

Unsupported

PasteRTF

 

Supported

PostEvent

 

Supported

Print

Mobile platform difference:

Supported in iOS, but unsupported in Android.

Unsupported

PrintCancel

 

Unsupported

ReselectRow

 

Supported

Reset

 

Unsupported

ResetDataColors

 

Unsupported

ResetTransObject

 

Supported

ResetUpdate

 

Supported

Retrieve

 

Supported

RowCount

 

Supported

RowsCopy

 

Supported

RowsDiscard

 

Supported

RowsMove

Events cannot be triggered while the application moves data within the primary buffer of one DataWindow.

Supported

SaveAs

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

  2. The supported SaveAs syntax :

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

    The unsupported SaveAs syntax:

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

    Note: For Appeon Mobile, when saveastype is PDF, the colheading and encoding arguments will be always executed as true and EncodingANSI!.

    For example, the following syntax:

    ds_1.SaveAs( filename, PDF!, false, EncodingUTF16BE! )

    will be executed as the following:

    ds_1.SaveAs( filename, PDF!, true, EncodingANSI! )
  3. If the DataStore without any data is saved as an HTML file, the header will not be saved in Appeon Mobile, whereas it will be saved on PB.

  4. When the file is generated via the SaveAs function on the mobile device, its file name is always in lower case, no matter which case you specify for the file name. This is as designed by Appeon Mobile. And since the mobile OS (such as iOS, Android) uses a case-sensitive file system, therefore, it is recommended you use lower case for the file name when developing an app for the mobile device.

  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.

Unsupported

SaveAsAscii

SaveAsAscii

Retainnewlinechar argument is unsupported.

Unsupported

SaveAsFormattedText

 

Supported

SelectRow

 

Unsupported

SeriesCount

 

Unsupported

SeriesName

 

Unsupported

SetBorderStyle

 

Supported

SetChanges

 

Supported

SetColumn

 

Unsupported

SetDataPieExplode

 

Unsupported

SetDataStyle

 

Supported

SetDetaHeight

 

Supported

SetFilter

 

Supported

SetFormat

 

Supported

SetFullState

 

Unsupported

SetHTMLAction

 

Supported

SetItem

 

Supported

SetItemStatus

 

Supported

SetPositon

 

Supported

SetRow

 

Unsupported

SetSeriesStyle

 

Supported

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.

Supported

SetSQLPreview

 

Supported

SetSQLSelect

 

Supported

SetText

 

Unsupported

SetTrans

 

Supported

SetTransObject

 

Supported

SetValue

The column argument works only if the edit style of the column is DropdownListBox.

Supported

SetWSObject

 

Supported

ShareData

 

Supported

ShareDataOff

 

Supported

Sort

 

Supported

TriggerEvent

The following TriggerEvent syntax is unsupported:

object1.TriggerEvent (object2, event)

Supported

TypeOf

 

Supported

Update

 


Table 219. Properties

Support Level

Feature Name

Description

Unsupported

ClassDefinition

 

Supported

DataObject

 

Supported

Object