Locking VSS Database

[nerickson]

I'm a little confused about when to lock my VSS database during the import process. If I lock VSS before I start the Import Tool it has a problem accessing the VSS database when I select the srcsafe.ini file.
Next when I get to the section where the Import Tool tells me who is logged into VSS and it tells that my database is not locked and that this is good. But if read the Import Tool User Guide it says "If the SourceSafe database is not locked, it is recommended that you do so now..." (This is located in page 11 of the Import Tool Guide under the Pre-Scan section).
So while the Import Guide tells me to lock VSS the Import Tool application tells me that it is good that my VSS database is not locked. I would think that it would be ideal to have VSS locked so that users would not be able to modify files but when should I lock VSS? Any insight into this would be great.

[lbauer]

You're right, the documentation is somewhat confusing. The SourceSafe database should not be locked when you launch the Import Tool and connect to VSS, etc. Be sure no one is logged into VSS at this time. Then, after the Prescan, you can lock the VSS database for the actual import of data.

I'll log a bug to clarify this in the Help.