BUG: REPLACE with UDF May Cause "Record Is Not Locked" Error
Article ID: 142397
Article Last Modified on 5/7/2003
APPLIES TO
- Microsoft Visual FoxPro 3.0 Standard Edition
- Microsoft Visual FoxPro 3.0b Standard Edition
- Microsoft Visual FoxPro 5.0 Standard Edition
- Microsoft Visual FoxPro 5.0a
- Microsoft Visual FoxPro 6.0 Professional Edition
This article was previously published under Q142397
SYMPTOMS
Using a user-defined function (UDF) that moves the record pointer in the
currently selected table with a REPLACE command causes a "Record is not
locked" error message. This error occurs if the buffering property is set
to 2-Pessimistic record, 3-Optimistic record, or 5-Optimistic table.
WORKAROUND
Set the buffering property to 4-Pessimistic table. This locks the record
and updates it after issuing the TABLEUPDATE() function.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article. We are researching this problem
and will post new information here in the Microsoft Knowledge Base as it
becomes available.
REFERENCES
For more information about the affect of SET EXCLUSIVE, please see the
following article in the Microsoft Knowledge Base:
125732 Cursor Created by User or ODBC Has EXCLUSIVE Status
For more information about the affect of READ NOLOCK, please see the
following article in the Microsoft Knowledge Base:
131031 READ NOLOCK Behavior in Visual FoxPro
Additional query words: kbvfp300 kbvfp500 kbvfp600
Keywords: kbbug kbprogramming KB142397