>I think you may have found the problem. I haven't verified that these files are read only with the client yet, but when I made them read only in my development environment, I got the exact same behavior as the client did.
>
>What surprises me is why VFP would let you use a database or table exclusively when the associated database container files are read only. You think VFP would give you some sort of "File Access Denied" error like it would if the DBF were read only. What situation would you ever have the database container files read only in a production environment?
>
>In any case, thanks for the help!
>
>Ben

You still end up with exclusive use (no one else can open the file), but you can't write to it. I guess the VFP god's did that by design..hahaha.
There are times when the database container ends up as read-only in a production enviornment. I have done this two ways in the past 1) I had the database container in source-safe on my development machine - when I copied it too production I had it 'checked-in', so it was flagged as read-only file. 2) I've manually changed them to read only on the production machine. I've done this to prevent anything (or anyone) from accidentaly making any changes