|
|
|
|
|
|
|
|
|
|
- Table control with direct access to the data source
- Table control populated programmatically
- Table control with in-memory data source
11. Table/Looper controls
Table/Looper controls can be used to display a set of information (e.g., the content of a data file). The content of these controls can come from three different sources: - Table/Looper controls with direct access to the data source,
- Table/Looper controls populated programmatically,
- Table/Looper controls with in-memory data source.
Note: The explanations in this page are based on the Table control. However, the same concepts apply to the Looper control. Table control with direct access to the data source A Table control with direct access to the data source directly displays data from a data file or query. The structure the data file is described in the data model editor and the data is entered in the application, for example. When you loop through the data file, the data is displayed in the Table control. For each row in the Table control, the data file is read and the data from each record is displayed in the corresponding row. The data that is not linked to the data file is lost when the Table control is refreshed (e.g. when scrolling through the table). The number of records displayed in the control can be limited by setting a filter ( HFilter used in the control initialization code). Several WLanguage functions can be used to manipulate Table controls based on a data file. These functions start with "Table". To add a record to the Table control, add the record to the corresponding HFSQL data file (using HAdd) and refresh the Table control with TableDisplay. To delete a record from the Table control, delete the record from the corresponding HFSQL data file (using HDelete) and refresh the Table control with TableDisplay. Table control populated programmatically In this case, the Table control directly displays the data loaded in memory. Data is added to the Table control programmatically, via different WLanguage functions ( TableAddLine, for example). When data is in memory, you can perform different actions in the Table control (sort columns, search in columns, etc.). Table control with in-memory data source Table controls with in-memory data source combine the advantages of Table controls with direct access to the data source and Table controls populated programmatically. The Table control is linked to the data file but the entire content of the data file is loaded in memory. Sort and the search features are available for all columns. The data that is not linked to the data file is not lost when moving the scrollbar (in Check Box columns, for example). Since the data file records are loaded in memory, this type of control is recommended for data files with less than 100 000 records (to avoid memory overflow). Note: The different modes to populate the controls (programmatically, with direct access to the data source and with in-memory data source) are available for different types of controls: List Box, Combo Box, Table, Looper, etc. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|