Matt,

Is it remotely possible that the person with the problem had someone access the table with FPx? Or maybe some other product that can handle DBFs?

I have avery vague memory of seeing thid message way back when I first installed VFP3.

Good luck,

JimN

>Hi Cetin,
>>At table level I don't expect a problem. Might it be a dbc compatibility problem ? If so backup and try a compile database. Next you could try copying the table to a separate dir and open exclusive (dbc not in path), when it asks to locate dbc, delete link and free table. You'd lose dbc level properties but basically you want data which you can append to an intact empty table.
>>PS: Honestly error msg itself is suspicious.
>
>Shouldn't be a compatibility problem - we distribute this table with our application and this is the first time anyone has found this problem.
>
>I tried putting the table in a separate directory as you suggest above, but exactly the same error comes up [there is no opportunity to locate the dbc even].
>
>I'm a bit puzzled - this client has had the application for over a year and this issue didn't arise in that time.
>
>Best.
>
>Matt.