The topics that document the CM tool integration in this help are generic using Microsoft Visual SourceSafe terminology. The following notes apply when working with Microsoft Visual SourceSafe.

We recommend that all Visual SourceSafe users use a shared srcsafe.ini file, which is the default for a client/server installation of Visual SourceSafe.

If users do not use a shared srcsafe.ini file and those users have different drive mappings for the Visual SourceSafe database the following problem can occur; if a user checks in a Package and another user with a different drive mapping views that Package, the Package icon will not have an arrow and the Check In command will not be available. To overcome this problem, the user will have to reconnect the Package using locally stored paths.

If you check out a Package, rename that Package in Modeler, and then check in that Package, the file name of the Package in the CM tool environment will reflect the new name of the Package, not the old name.

If you are working with Microsoft Visual SourceSafe version 6.0d, you must install a Microsoft patch to work with the Modeler CM Tool integration.