PRB: Moving Project in SourceSafe Explorer Causes Error in VB

 Last reviewed: February 28, 1997
Article ID: Q135720
4.00 5.00 | 4.00 5.00 WINDOWS NT | WINDOWS kbusage kbprb

The information in this article applies to:

  • Microsoft Visual SourceSafe for Windows NT, versions 4.0, 5.0
  • Microsoft Visual SourceSafe for Windows 95, versions 4.0, 5.0
  • Microsoft Visual SourceSafe for Windows, versions 4.0, 5.0
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic for Windows, 16-bit and 32-bit, version 4.0

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"

CAUSE

The project was open in Visual Basic when it was moved or renamed in the Visual SourceSafe Explorer. Because the project was moved or renamed, the SourceSafe Add-In in Visual Basic can no longer can find it.

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.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

  1. In Visual Basic, open a sample project, and add it to Source Code control.

  2. In Visual Basic, run the SourceSafe Explorer. (On the Add-Ins menu, click SourceSafe and then Run SourceSafe.

  3. In the Visual SourceSafe Explorer, move the project to another location, such as into a subdirectory.

  4. In Visual Basic, check out the files. The following error message displays:

    All available files have already been checked out.

Of course, you know the files are not checked out, neither in Visual Basic nor the Visual SourceSafe Explorer.

REFERENCES

For more information on synchronizing Visual SourceSafe with Visual Basic, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q135357
   TITLE     : PRB: Sync Between Visual SourceSafe and VB Is Delayed

KBCategory: kbusage kbprb
KBSubcategory: SourceSafe ssvb vbwin VB
Additional reference words: 4.00 5.00
Keywords : SourceSafe ssvb VB vbwin kbprb kbusage
Version : 4.00 5.00 | 4.00 5.00
Platform : NT WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.