Hello Sandro,

I have found over many years of using VFP with VSS that it is best not to put the database or table in VSS. If you do so, you are constantly having to deal with VSS setting all of your tables to read-only unless they are "checked out".

The best course is to create a master database with a master set of tables on a shared drive somewhere and make all changes to the master set, copying the changes to local drives as needed.

It may get more complicated than this if your tables are populated with test data. Then, in addition to keeping an empty set of master tables, you will also have to write a conversion program that obtains the empty structure of any master tables, copies them to the local drive, appends data from the local table into the changed table, and deletes the old table. We usually end up converting tables at least once a week, so the entire process is automated based on version number.

There may be a better way of doing this, but I have not found it yet.

Regards,