When to Use Application Mode

If you do not want to use a bound data source control to populate the list, either one of the following DataMode settings is ideally suited to the task:

2 - Unbound Extended, which fetches multiple rows in a single event,

3 - Application, which fires events on a cell-by-cell basis,

The choice comes down to efficiency versus ease of implementation. If you are concerned about efficiency, and would like to minimize the number of events that fire, you should consider using DataMode 2 - Unbound Extended. Mode 2 is also recommended when using database APIs that support multiple-row fetches, such as ODBC.

If you are migrating from DBList and find DataMode 1 - Unbound difficult to use, you should consider switching to application mode, as it provides the same benefits, but is much easier to implement.

If your data source is a two-dimensional array, you should use DataMode 4 - Storage, as it was specifically designed for this purpose.

If you are familiar with the Fetch callback event of TrueGrid Pro (TRUEGRID.VBX), then application mode is recommended, as the style of coding is very similar. In fact, the "classic" events are so named because they were patterned after the callback mode events of TrueGrid Pro.