Visual SourceSafe 6.0 Solution Center

Get Visual Studio 6.0 Service Pack 6
Microsoft Service Pack 6 for Visual Basic 6.0, Visual C++ 6.0 with Visual SourceSafe 6.0d addresses known issues with Visual Basic 6.0, Visual C++ 6.0 and Visual Source Safe 6.0. This service pack does not contain fixes for Visual InterDev 6.0, Visual FoxPro 6.0, and Visual J++ 6.0, as the mainstream life-cycle for these products has ended.

How To Change the Data Directory Location
To move the SourceSafe data directory to a location different from the SourceSafe location, follow these steps: Copy the DATA directory to the new directory.IMPORTANT: Make sure you copy all subdirectories even if they are empty. SourceSafe will...
INFO: How SourceSafe Selects a Viewer for a File
To check settings to select a viewer for a file, SourceSafe follows these steps in order: Uses SRCSAFE.ini or SS.ini settings for selected extension. For example: .DOC = C:\WINWORD\WINWORD.EXE %1 Uses Editor setting in SRCSAFE.INI or SS.INI to set...
HOWTO: How to Create a New Database in SourceSafe
Use the Mkss.exe in the ADMIN sub-directory to create a new SourceSafe database by following these steps: Create a target directory for the new database.Run MKSS <directory>.Run DDCONV <directory>. You do not need to use the following step with...

FIX: History of a Label Does Not List the Files from Subproject
When you label a project, and then view the label in the history of a subproject, the files that are included in the label from that subproject do not appear in the list. Visual SourceSafe 6.0321139INFO: List of Bugs Fixed in Visual SourceSafe 6.0...
FIX: Integration of Visual SourceSafe, Visual InterDev, and FrontPage does not succeed and the file does not appear to be under source control
If a user saves a file in Microsoft FrontPage or Microsoft Visual InterDev, the vti_sourcesafeversion line and the vti_sourcesafecookie line are removed from the file's metadata. The file is still saved to the site and the user does not receive an...
FIX: Analyze -F Causes Inconsistencies if 10 Multibyte Character Set Files with First Eight Bytes Are the Same Text
Analyze.exe -F causes the following inconsistency error message if the Visual SourceSafe (VSS) database contains 10 multibyte character set (MBCS) files with the same first eight text bytes and, if there is a long file name with the first eight bytes...

BUG: Variable Uses Automation Type Not Supported Error
When you try to add a Microsoft SQL Server 7.0 Stored Procedure to Source Control, you receive the following error message: Note In this error message, the word "eror" is a misspelling for the word "error."
PRB: Branching Files in SourceSafe Causes Lost Disk Space
Destroying projects and/or files from SourceSafe does not free disk space in SS\DATA subdirectories. Once a file is branched in SourceSafe, there are four associated files that are not deleted from the disk at this point. The reason this occurs is...
PRB: Lock_Mode = lockfile Causes "Timeout Locking File" Error
A "Timeout Locking File" error occurs if the SRCSAFE.INI file contains Lock_Mode = lockfile. This error indicates a lock file (.LCK extension) exists in the DATA\LOCKS directory. This situation occurs under either of the following circumstances: A...