SYMPTOMS
In Visual Basic, when you run the SourceSafe CheckOut Command, the
following error message displays in Visual Basic:
All available files have already been checked out.
RESOLUTION
In the Visual SourceSafe Explorer, when you run SourceSafe commands that
impact a project open in Visual Basic, click Refresh File Status on the Add-
Ins / SourceSafe menu. By refreshing the project file status, Visual Basic
is able to get in sync with Visual SourceSafe.
If you run Refresh File Status after the series of steps listed in the
"Steps to Reproduce Behavior" section of this article, this message
appears:
Project <old VSS project location> has been moved or renamed to <found
VSS project location>. Would you like to connect to this project?
This project location may or may not be the project you want. In most
cases, it probably is, so you can click OK and you continue on with your
work.
If you click Cancel, the following error message displays:
Project <old VSS project location> was not found. Would you like to
browse for the project?
If you know the new location or new name for the file, click Yes, and
select the new project location or name. If you click No, the following
error message displays:
The project "<old VSS project location>", <VSS Database File> no longer
exists in SourceSafe. You must either recover or re-create the project
before you can use this project with source code control.
At this point, there is no longer any link between any Visual SourceSafe
project and the project you currently have open in Visual Basic.
REFERENCES
For more information on synchronizing Visual SourceSafe with Visual Basic,
please see the following article in the Microsoft Knowledge Base:
135357 PRB: Sync Between Visual SourceSafe and VB Is Delayed