BUG: REPLACE with UDF May Cause "Record Is Not Locked" ErrorID: Q142397 The information in this article applies to:
SYMPTOMSUsing 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.
WORKAROUNDSet the buffering property to 4-Pessimistic table. This locks the record and updates it after issuing the TABLEUPDATE() function.
STATUSMicrosoft 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.
MORE INFORMATION
Steps to Reproduce Problem1. Create a program called Test.prg containing the following code:
2. Run the program. The error "Record is not locked" appears after
REFERENCESFor more information about the affect of SET EXCLUSIVE, please see the following article in the Microsoft Knowledge Base:
For more information about the affect of READ NOLOCK, please see the
following article in the Microsoft Knowledge Base:
KBCategory: kbprg kbbuglist
KBSubcategory: FxprgGeneral vfoxwinbuglist3.00 buglist3.00b buglist5.00
Additional reference words: 5.00 3.00 3.00b kbvfp300 kbvfp500 kbvfp600
|
Last Reviewed: August 10, 1998 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |