Updating Data with the RDO RemoteData Control
The new home for Visual Studio documentation is Visual Studio 2017 Documentation on docs.microsoft.com.
The latest version of this topic can be found at Visual Studio 2017 Documentation. RDO RemoteData control data can be either read-only or modifiable.
To create an application that modifies data using RDO RemoteData control
Set the RDO RemoteData control CursorDriver property.
Server Side cursors store returned data on the server.
ODBC Client Side cursors store data in the client's local storage.
Client Batch Side cursors use a cursor library designed to deal with concurrency issues.
No Cursor option is used when an action query is performed, and thus no cursor is necessary.
Set the RDO RemoteData control LockType property. The optimistic concurrency based on resultset option is recommended.
Read-only concurrency should not be used if you want data to be modifiable.
Pessimistic concurrency locks data during update so that other users are not in danger of committing incompatible data changes.
Optimistic concurrency does not lock data, but if during commit, it detects that another client has posted an incompatible state, the RDO RemoteData control throws an error.
Set the RDO RemoteData control ResultsetType property. Make sure the ODBC driver supports the chosen options:
When Create Static Cursor is chosen, the changes are not detected until the cursor is closed and reopened.
When Create Keyset Cursor is chosen, the cursor allows inserts, updates, and deletes, at will, within the keyset cursor itself.
Set the data-bound control as needed to allow updateability. Note that some controls do not allow updating.
For information about how to use these objects, see the documentation about the RDO RemoteData control.