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.Įach chunk of records is accumulated on the client as a local cache of records. This allows the end-user to browse the first 100 records locally. This property defines the number of records to be passed to the client upon each request for additional records.įor example, if this property is set to 100, when the task opens, the server will pass the first 100 records to the client. 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. Once the value is set to TRUE, the server will fetch all relevant records from the database during task initialization. This property defines whether to retrieve the entire data view in advance.
This is explained in more detail in Transactions. Must be Deferred or Within Active Deferred. If there is no icon defined for the task, the icon displayed will be the icon defined in the application properties. This section describes some of these settings:Īs 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.Īs with a regular Online task, you can define an icon to be displayed in the Rich Client task. However, other settings are only relevant for a Rich Client task. Most Rich Client task settings are the same as the settings of an Online task although some Online task settings are irrelevant to a Rich Client task.
0 kommentar(er)
