ezds.com : Free SourceSafe tool ssrights : Show a user's project rights or lack of rights.

ssrights

ZDS

SourceSafe Tools

Purpose	For a specified SourceSafe user the tool will list projects that are accessible or inaccessible. Why would you want to know what rights a user doesn't have? As an administrator you need to be sure that SourceSafe commands you run will execute without fail against every project in the database. This will not be the case unless you have rights to every project. For example if you use ss dir to list a project to which you do not have rights it will list the project as containing no files when in fact there are files in the project! The tool is also useful in resolving differences between the number of projects listed by ssdir and ssphysical.
SS	Tested with SourceSafe V5.0 V6.0
OS	Windows NT/2K/XP Command line utility.
Usage	ssrights v1.61 syntax {optional} ssrights $/SourceSafeProjectPath -YUserlogon,Password -R{Y or N} {$/SourceSafeProjectPath} Use forward slashes default -RN List projects for which user does not have access rights -RY List projects for which user has access rights Examples: complete tree : ssrights $/ -YFmanchu,sesame sub tree : ssrights "$/Test" -Ydgoodall,sesame -RY
Outputs	Analysis of SourceSafe Project Rights Sun Mar 11 14:56:39 2001 Projects to which dgoodall does NOT have access rights in $/ File Project Count 0 $/Test/Project1/Sub2 0 $/Test/Project2 dgoodall does not have access rights to 2 out of 14232 projects in the $/ tree
How it Works	The program works by running two comand line commands and comparing the results. ss dir is used to generate a list of projects. A project may really have no files or just appear to have none as the user does not have rights to the project. ss history is used to identify projects that are not accessible to the user, allowing the tool to figure out which of these possibilities is the case. The tool is not fast, but it does get the job done.
Installation	Copy the program into the directory where you want to run it. It's stand-alone and requires no configuration or support.
Credits	Thanks to Simon Ferguson of eps-software.com who noticed that the batch files could halt waiting for user input e.g: E:\Shared\VSS\Utilities>ss history "$/CIA/admin" -V0 -YPopeye,spinach -ossrights.$$2 Project $ADMIN has been destroyed, and cannot be rebuilt. Continue anyway?(Y/N) In version 1.5 the -I switch has been added to the batch files to remove the need for users to have to hit Y to continue.
Download	ssrights 1.61 (34 KB)