Is it possible to open a table within a database for exclusive use without preventing other users from opening other tables in the same database for shared use?
As it stands now, when I try to open a table for shared access when another user has some other table open for exclusive use, VFP claims I'm trying to get write access to the .DBC that contains both.
I can understand why this might be happening, and depending on how VFP implements databases, why this might be a fact of life.
I was just wondering if there is a way to configure things so that someone's exclusive use of a database table doesn't prevent me from using another table that's in the same database.
???
"The Iron Fish: The water is cold...but the fish don't mind"
...Jay Jenks, boyhood chum