...
"subfile changed": Specifies a response indicator that is set on if the input data within the subfile is modified.
...
Message Subfile Settings
"font family": The font face for the text inside the grid. To define a different font for each grid column, select <i>Other...</i> and specify a comma separated list of fonts.
...
subfile message key": This property specifies a field that is used to select messages from a program message queue for display. Your program places a message reference key in this field. The property represents the SFLMSGKEY keyword on a subfile record format.
"subfile program message queue": This property specifies a field that contains the name of the program message queue used to build a message subfile. It represents the SFLPGMQ keyword on a subfile record format.
"subfile control program message queue": This property specifies a field that contains the name of the program message queue used to build a message subfile when used in conjunction with the subfile initialize property. It represents the SFLPGMQ keyword on a subfile control record format.
Font and Text
"font family": The font face for the text inside the grid. To define a different font for each grid column, select <i>Other...</i> and specify a comma separated list of fonts.
- Possible choices: "Arial", "Consolas", "Courier New", "Fantasy", "Georgia", "Monospace", "Tahoma", "Times New Roman", "Sans-Serif", "Serif", "Trebuchet MS", "Verdana", "Other..."
...
"scroll tool tip": Determines if the row number or the row number range should be displayed in a tool tip when the user scrolls through the data in the gridif the row number or the row number range should be displayed in a tool tip when the user scrolls through the data in the grid.
- Possible choices: "none", "row number", "row range"
"propagate scroll events": When this property is false (which is the default) the grid handles any scroll wheel or swipe events sent to it so that they scroll the grid, but not the window that the grid is placed inside. If you enable this property, these events will be propagated, which allows mouse wheel and swipe events to scroll the grid's parent window.
- Possible choices: "nonetrue", "row number", "row rangefalse"
"sortable columns": Enables column sorting. If set to true, the user will be able to click on the column headings to resort the data.
...
"database file": Database file to use for a grid that is tied directly to a database. You can specify a 'database file' or 'library/database file'. If library is omitted, the session's library list is used."database fields": A set of database field names omitted, the session's library list is used.
"database fields": A set of database field names to use to retrieve the data for a database-driven grid. The field names should be comma separated.
"selection criteria": Optional expression identifying which records should be retrieved from the database file.
"order by": Optional expression identifying which fields determine the order of the records retrieved from the database file.
"custom sql": Specifies an sql statement to use to retrieve the data records for a database-driven grid. The field names should be comma separated.
"selection criteria": Optional expression identifying which records should be retrieved from the database file.
"order by": Optional expression identifying which fields determine the order of the records retrieved from the database file.
"custom sql": Specifies an sql statement to use to retrieve the records for a database-driven grid
"allow any select statement": Allows any valid SELECT SQL statement. If this is false (default), a row count is retrieved by running SELECT COUNT( *) FROM (your-custom-sql-property), so your "custom sql" property must work with that syntax. This prevents the use of common table expressions, the optimize clause, and a few other things. If set to true, the row count will be determined by running your statement as-is and looping through all rows to count them. Note: False performs better, but true allows a wider variety of SQL statements.
"parameter value": Value for parameter marker in "selection criteria" or "custom sql" property. Parameter markers are specified using a question mark. Profound UI will accept values from the client for any parameter marker values which are not bound to program fields. Parameter markers are numbered in order of occurence, from left to right. To specify multiple parameter marker values, right-click the property and select Add Another Parameter Value.
...
"tool tip": Defines the text to appear in a tool tip when the user hovers the mouse over this element.
"user defined data": Specifies user-defined general purpose data associated with the widget. To provide multiple user defined data values, right-click the property and select Add Another User Defined Value.
"visibility": Determines whether the element is visible or hidden.
...