How Transaction Processing Affects Record Locking

Last reviewed: April 30, 1996
Article ID: Q126870
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, version 3.0

SUMMARY

Record and file locking behavior is slightly different when transaction processing is used in Visual FoxPro.

MORE INFORMATION

When 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:

  • Open all tables before issuing the BEGIN TRANSACTION command. This prevents the entire table from being locked as soon as it is opened.
  • Buffering should be enabled and all edits performed before the transaction starts. The BEGIN TRANSACTION command should be issued immediately before a TABLEUPDATE() or a SQLCOMMIT() function. Optimistic row buffering provides the shortest locking time of all buffering types. However, table buffering must be used if you wish to rollback multiple transactions.
  • Avoid the use of commands with a FOR scope within the confines of a transaction, since these commands lock the entire database. If you must use commands such as REPLACE within a transaction, use a SCAN loop to perform individual commands instead.
  • Close the transaction as soon as possible after the update has been applied to the table.

REFERENCES

For 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
KBCategory: kbprg
KBSubcategory: FxprgMultiuser


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 30, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.