See SET TABLEVALIDATE command. With default setting VFP trys to lock a table header on USE to validate the table record count against actual # of records in the table.

>Has then been a change in the way SHARED work with a USE statement from VFP 6 to VFP 9? Here's what I'm seeing, I have a dbf open, from the VFP 6 enviornment I can issue the following:
>
>

USE table AGAIN IN 0 SHARED

>
>and am able to successfuly open that dbf. But, from the VFP 9 enviornment it sits as it is "Attempting to lock" the file. With this same type of USE statement used in our application, we recieve an Error 108: File is in use by another user, but with VFP 6 this worked and was allowed to open the file again.
>