The only locking occurs during
the split second when the update is actually written to the Access table. Thus, when No
Locks is set, someone may be able to start an edit but may not be able to finish it. The No
Locks setting is most appropriate in environments where users will be adding many
records simultaneously. This will allow all adds to be started and almost all updates to be
committed (unless two people save the record at the same time). Your error-handling routines
must anticipate the errors that occur when the record is committed. The No Locks
setting is called optimistic locking because you have every expectation that the record commit
will proceed without error.
n All Records: The All Records setting locks an entire recordset as long as the user has the
table, form, or query open for viewing. This setting really has no practical use in a
dynamic multiuser environment. The only time it should be used is when you??™re doing
some kind of administrative updates to a table and don??™t want anyone else editing records
during the time you are updating.
Pages:
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373