MX-Frame Library Send comments on this topic.
Consistency
See Also
MX-Developer > Data Access Layer - MxAdapter > Designing Data Source > Consistency

Glossary Item Box

Data is consistent if it does not contain contradictions. Therefore data is consistent if data displayed is equal to data stored in its data source.
 
To ensure consistency of data in a data source, consistency key must be defined. According to this consistency key system compares consistency timestamp of displayed field to a consistency timestamp of a field in a data source. If timestamps differs warning is displayed to the user, through grid notification, informing the user about the data inconsistency. User can than decide what to do. User can than reload data, lock record, reject changes etc.

Defining properties appropriately it is possible to specify the manner in which consistency will be checked and the action executed if the inconsistency is determined.

Developer can define the behaviour of the data source after inconsistency is determined. It is possible to refresh data or to only check them. Furthermore it is possible to define the action for every type of inconsistency. With properties Added, Changed and Missing it is possible to define what to do if a new record is added, a record is changed or a record is deleted.

Options that can be selected for these properties are None, Lock and Override.

Developer can also define which record remains selected after a new record is added or a record is removed. This is defined with property PositionRetain

An interval for consistency checking can be defined with property Interval. The value defines the number of milliseconds.

See Implementing Consistency chapter for the step by step instruction how to implement a consistency feature.

See Also

©2009 Metronik. All Rights Reserved.