MOD2000: Excel Objects in Visual Basic Editor Lose Connectivity to Visual SourceSafe When You Rename The Objects (259607)
The information in this article applies to:
- Microsoft Office 2000 Developer
This article was previously published under Q259607 SYMPTOMS
If you rename a Microsoft Excel worksheet or VBA project that you have placed under Microsoft Visual SourceSafe control, the object is removed from source code control. When you try to check the object back into Visual SourceSafe after you rename the object, you receive the following error message:
You do not have any files checked out from Source Code Control.
If you rename the object back to its original name, Visual SourceSafe control is reinstated over the object.
RESOLUTION
If you must rename an object that is currently under Visual SourceSafe control, first remove the object from the Visual SourceSafe database. After you have renamed the object, check the object back into Visual SourceSafe under its new name.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 6/26/2001 |
---|
Keywords: | kbbug KB259607 |
---|
|