>>>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.
>
>Erik. I remember you having this error a few months back. Did you ever figure it out?

Actually, I think you are referring to the thread on error 1709 "Database object is in use by another". These are two really different beasts. 1709 is caused by two users attempting to open a view at the exact same time. Since VFP momentarilty locks the record in the dbc, it causes contention.

The error in quesion in this thread is also a record locking error, but it is usually the program code at fault. In multi-user environments, it can usually be resolved with SET REPROCESS TO AUTOMATIC, but in a single user environment, I strongly suspect there is some funky code at fault.