>It's been discontinued. No more updates.

But Craig, I think we can say the same for FoxPro - No more updates.

I'm finding that SourceSafe 6.0d and SourceSafe 2005 are in good enough shape that they don't need updates from the Mothership.

Once a month I run the Analyze utility to look for problems, which is a recommended Standard Practice. About every 1.5 years are there any problems and the utility fixes them.

Here is a copy of my Analyze BAT file. You'll need to change the location of your SourceSafe database.

@echo off
:*********************************************************
:jeff leason
:20050408
:
: This needs to be run once a month to make sure the VSS
: doesn't have problems.
:
: Users should be out of VSS.
: The Admin can lock VSS but don't forget to unlock it.
:*********************************************************
echo.
echo You are about to run the VSS Analzye Utility.
echo This checks and fixes corruption in the VSS Database.
echo This process takes about 10 to 20 minutes or more.
echo.
echo Make sure all the users are out of VSS or VFP projects that might be in VSS.
echo.
echo Press CTRL-C to cancel now
echo.
pause

if exist K:\Development\SOURCESAFE\data\backup\. goto ren_back
C:
cd "C:\Program Files\Microsoft Visual SourceSafe"
analyze -REFV6 -v4 K:\Development\SOURCESAFE\data

echo.
echo Make sure you run this utility a second time if fixes were made.
pause
goto end


:*******************************
:ren_back
:*******************************
cls
echo.
echo Sorry!
echo.
echo First you need to rename the existing t:\sourcesafe\data\backup folder
echo before you can run VSS Analyze
echo.
echo For example: K:\Development\SOURCESAFE\data\backup20050415
echo.
pause

:*******************************
:end
:*******************************
cls
echo.
echo IMPORTANT!!!
echo IMPORTANT!!!
echo.
echo Be sure to remember to Unlock the VSS Database if you locked it.
echo.
echo IMPORTANT!!!
echo IMPORTANT!!!
echo.
pause

:*******************************
:final
:*******************************