Using SpeedMode

Applies to: Apollo VCL™

The SpeedMode property in TApolloTable is a little known secret. Setting it makes the VCL layer as thin as possible over the underlying SDE API. Without it, a call to the Replace method for example goes through the TDataSet class' SetFieldData procedure and other FieldDef-related routines, thereby adding overhead. In SpeedMode, the Replace method is mapped directly to the sx_Replace function with minimal other activity.

The caveat is that all UI controls, namely data-aware controls, do not get updated with the underlying data as it is being traversed or updated. Essentially SpeedMode disconnects the data-aware controls from being updated by Apollo VCL and the SDE. This is not to be confused with the DisableControls and EnableControls methods. If you use DisableControls and EnableControls only, Apollo still updates the various VCL UI and data buffers behind the scenes.

So, if you're looking for a way to boost performance on data access involving traversing or updating large data sets, try using SpeedMode.