Visual Basic: RDO Data Control
UpdateCriteria Property
See Also Example Applies To
Returns or sets a value that specifies how the WHERE clause is constructed for each row during an optimistic batch update operation.
Syntax
object**.UpdateCriteria** [= value]
The UpdateCriteria property syntax has these parts:
| Part | Description |
| object | An object expression that evaluates to an object in the Applies To list. |
| value | A Long integer representing the type of cursor as described in Settings |
Settings
The UpdateCriteria property has these settings:
| Constant | Value | rdoResultset type |
| rdCriteriaKey | 0 | (Default). Uses just the key column(s) in the where clause. |
| rdCriteriaAllCols | 1 | Uses the key column(s) and all updated columns in the where clause. |
| rdCriteriaUpdCols | 2 | Uses the key column(s) and all the columns in the where clause. |
| rdCriteriaTimeStamp | 3 | Uses just the timestamp column if available (will generate a runtime error if no timestamp column is in the result set). |
Remarks
When a batch mode operation is executed, RDO and the ClientBatch cursor library create a series of UPDATE statements to make the needed changes. An SQL WHERE clause is created for each update to isolate the rows that are marked as changed (by the Status property). Because some remote servers use triggers or other ways to enforce referential integrity, is it often important to limit the columns being updated to just those affected by the change. This way, only the absolute minimum amount of trigger code is executed. As a result, the update operation is executed more quickly, and with fewer potential errors.
You should set the UpdateCriteria property to rdCriteriaKey when BLOB columns are included in the result set.
Setting this property to a value other than the ones listed here results in a runtime error.