>Does anyone know what this error in VFP 3 really means? This is a previously well behaved app: I have about 10 tables open, and am appending to one of the tables from a table not in use. There is a stored procedure that SELECTS the ids from the open table in order to come up with a new unique ID. I didn't change this part of the code (arrg), and it works fine in VFP 5. Something I'm missing here? This is a single-user app, and EXCLUSIVE is ON.
>
>
>I love the Microsoft documentation on this: the explanation is that the application cannot write to a record in use, which is exactly what the error message says.

Basically, the message says that implicit lock has been already applied to the record the app tries to write in now. It might be strange behaviour (bug or feature??) caused by different data sessions going to the same table.record. BTW I understand that this explanation is too fancy.