PRB: Error When Renaming a File That Is Checked Out

 Last reviewed: November 11, 1996
Article ID: Q158701
The information in this article applies to:
  • Microsoft Visual SourceSafe, 32-bit, for Windows, versions 4.0, 4.0a, 5.0

SYMPTOMS

Visual SourceSafe 4.0

If you rename a file that is checked out in Visual SourceSafe 4.0, and you try to check it back in, you get the following message: 

   File "<working directory>\<filename>" not found
Where <working directory> is the working directory for the renamed file, and <filename> is the new name of the file.

This behavior occurs because the copy of the checked-out file is not renamed by Visual SourceSafe.

Visual SourceSafe 5.0

If you try to rename a file that is checked out in Visual SourceSafe 5.0, the following message appears: 

   Unable to rename the selected file
If you try to rename a file that is checked out to another user, the same message appears.

RESOLUTION

Before renaming a file in the Visual SourceSafe database, make sure that the file is not checked out by any users.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

Visual SourceSafe 4.0:

  1. Open or switch to Visual SourceSafe 4.0.

  2. Right-click a file and click Check Out.

  3. With the checked-out file selected, click Rename on the File menu.

  4. Rename the file.

  5. Right-click the file and click Check In. Note that the following message appears: 

          File "<Working directory>\<filename>" not found

Visual SourceSafe 5.0:

  1. Open or switch to Visual SourceSafe 5.0.

  2. Right-click a file and click Check Out.

  3. Right-click the checked-out file and click Rename. Note that the following message appears: 

          Unable to rename the selected file

KBCategory: kbprg kbprb
KBSubcategory: ssui
Additional reference words: 4.00 4.00a 5.00 kbdss



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: November 11, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.