Erik,

I get this occasionally on a multi-user app that has complete optimistic buffering/locking everywhere and not much traffic relatively speaking. In theory - it shouldn't EVER happen, but there is obviously something going on that causes it - since it is not reproducible, and never happens in the same way twice - it is very hard to debug

Ken

>>I have an application that periodically gets this message. The app is running on a single computer, on the harddrive of that machine. There is not more than one Foxpro session running. The table is open with tablebuffering. This is not much info but I don't know what else to say. This message should indicate another user locking the record, but this is not the case.
>>
>
>
>It would be much moe helpful if oyu could tell us what line of code or what user event is causing the error.