MOD2000: "File Not Found" Error When You Check in File from Visual SourceSafe Explorer (234830)


The information in this article applies to:

  • Microsoft Office 2000 Developer
  • Microsoft Visual SourceSafe for Windows 6.0
This article was previously published under Q234830

SYMPTOMS

In Visual SourceSafe Explorer, if you try to check in a Microsoft Office object, you may receive the following error message:
"File <filename> not found."

CAUSE

The object was previously checked out in the Visual Basic Editor with the Source Code Control add-in. The VBA Source Code Control add-in does not create a local file for each object in a source code control project. Objects are managed as part of their container document, workbook, or presentation.

RESOLUTION

Check all objects in and out of source code control with the VBA Source Code Control add-in in the Visual Basic Editor. Avoid checking these objects in with Visual SourceSafe Explorer.

MORE INFORMATION

Steps to Reproduce the Behavior

  1. Create and save a new workbook in Microsoft Excel 2000.
  2. Open the Visual Basic Editor (press ALT+F11).
  3. Use the VBA Source Code Control add-in to add the workbook and the sheets it contains to source code control. To do so, on the Add-ins menu, point to VBA Source Code Control, and then click Add Project to SourceSafe.
  4. Use the VBA Source Code Control add-in to check out Sheet1 (right-click Sheet1, and then click Check Out).
  5. Start Visual SourceSafe Explorer. On the Add-ins menu, point to VBA Source Code Control, and then click Run SourceSafe.
  6. Try to check in Sheet1 by using the Visual SourceSafe Explorer ( right-click Sheet1, and then click Check In). Note that you received the following error message:
    File "<path>\Sheet1.cls" not found
Modification Type:MajorLast Reviewed:5/3/2001
Keywords:kbprb KB234830
©2002 Microsoft Corporation. All rights reserved.