Main Display

As with a regular Online task, you can define several forms and, using the Main Display property, you can provide an expression that evaluates to the form number.

Icon File Name

As with a regular Online task, you can define an icon to be displayed in the Rich Client task. If there is no icon defined for the task, the icon displayed will be the icon defined in the application properties.

Transaction Mode

Must be Deferred or Within Active Deferred. This is explained in more detail in Transactions.

Preload View

This property defines whether to retrieve the entire data view in advance. Once the value is set to TRUE, the server will fetch all relevant records from the database during task initialization. This is very useful for small tables.

When Preload View is set to TRUE, it is good practice to make the chunk size large enough to hold all the records fetched from the database.

Chunk Size Expression

This property defines the number of records to be passed to the client upon each request for additional records.

For example, if this property is set to 100, when the task opens, the server will pass the first 100 records to the client. This allows the end-user to browse the first 100 records locally. When the end-user tries to scroll beyond a given range of records, the client contacts the server and receives an additional batch of 100 records.

Each chunk of records is accumulated on the client as a local cache of records. If the end-user goes to the end or beginning of the table, the local cache is cleared and the cache accommodates a single batch of records.

Database specific: The chunk size is not supported for local databases.

Note:

Defining a chunk size that is too large may slow performance. For each data transfer, a lot of data will be passed from the server to the client.

On the other hand, if the record length is large (for example, it may contain a number of large Blob variables) you might want to consider decreasing the chunk size.