How Transaction Processing Affects Record LockingLast reviewed: April 30, 1996Article ID: Q126870 |
The information in this article applies to:
SUMMARYRecord and file locking behavior is slightly different when transaction processing is used in Visual FoxPro.
MORE INFORMATIONWhen you issue a BEGIN TRANSACTION command, the index of the currently open table is locked. Only the current user is able to update, add, or delete records in the table while the transaction is in progress. Any command or function that normally places a lock will continue to do so. Automatic locks are released automatically when the transaction is completed. Either a ROLLBACK or END TRANSACTION command must be used to end the transaction. Manual locks - those placed with LOCK(), RLOCK() or FLOCK() - must be manually released after the transaction is completed. This behavior is by design, and is required to ensure the basic functionality of transaction processing. The following coding techniques can be used to minimize contention for record locks:
REFERENCESFor more information on buffering and transaction processing, refer to the Microsoft Visual FoxPro "Developers Guide," or to the following commands and functions in the "Language Reference":
BEGIN TRANSACTION END TRANSACTION ROLLBACK CURSORSETPROP() TABLEUPDATE() TABLEREVERT() SQLSETPROP() SQLCOMMIT() SQLROLLBACK() |
Additional reference words: 3.00 VFoxWin
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |