The information in this article applies to:
In browse mode, it is possible for user 1 to determine that user 2 has made a change to a row without actually issuing an update to that row. You do this by issuing a select with the same WHERE clause (constructed by dbqual) that would have been used for the update. If the select returns a 532 error, the timestamp has changed since you last read the row. If you use this technique, be aware that there is no protection against another user changing the row right after it is tested, unless you select with HOLDLOCK. Additional query words: DB-Library db-lib dblib
Keywords : kbprg SSrvDB_Lib |
Last Reviewed: March 6, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |