The information in this article applies to:
SYMPTOMSRLOCK() will not function properly when a FoxPro Application and a Clipper Application access the same table simultaneously. CAUSEBoth FoxPro and Clipper have their own Locking Mechanism. When applying a lock to a table file on the Network, the function FLOCK() can be recognized by both Foxpro and Clipper; it will return a TRUE (.T.) if the table is locked by any of the applications. The function RLOCK() returns a TRUE only if a particular record of a table is locked by the same application. In other words, if a record was locked by Foxpro, Clipper can still lock the particular record without an error, and it has the same behavior the other way around. RESOLUTIONUse FLOCK() instead of RLOCK(). MORE INFORMATIONSteps to Reproduce BehaviorRun the following code in Clipper:
and Run the following code in FoxPro:
Expected BehaviorWhen the above code is executed by Foxpro and Clipper at the same time, the expected behavior is:
Actual Behavior
Additional query words: FoxWin VFoxWin FoxDos
Keywords : kb3rdparty FxinteropDatabase |
Last Reviewed: August 20, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |