Visual SourceSafe 6.0 Solution Center

Top issues

  • 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 articles - Visual SourceSafe 6.0

how-to articles - Visual SourceSafe 6.0

  • 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...
  • 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...
  • 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...
Download details - Visual SourceSafe 6.0

Download details - Visual SourceSafe 6.0

Troubleshooting - Visual SourceSafe 6.0

Troubleshooting - Visual SourceSafe 6.0

  • 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...
Last Review : December 8, 2007