BUG: Cannot Add a Secured VBA Module to SourceSafe. (214607)
The information in this article applies to:
- Microsoft Visual SourceSafe for Windows 6.0
- Microsoft Office 2000 Developer
This article was previously published under Q214607 Moderate: Requires basic macro, coding, and interoperability skills.
SYMPTOMS
When adding a password protected Visual Basic for Applications (VBA) project to SourceSafe, you will see one of the following errors. The error you see depends on whether the VBA project is part of an Access 2000 database or one of the other Office 2000 applications.
- When adding an Access 2000 module to SourceSafe the following error message appears:
Failed to export <object name> to a file.
- When adding an Office 2000 VBA project (non-Access) to SourceSafe the following error message appears.:
The addin was unable to retrieve information about the current project and cannot continue.
If you attempt to add to SourceSafe again, the following error message appears:
50289: Can't perform operation since the project is protected.
CAUSE
SourceSafe cannot display the Password dialog box for the project. Therefore, the project can not be opened for insertion into the VSS database.
RESOLUTION
Manually open the project in the Visual Basic Editor (VBE) and supply the password when prompted. Once the project has been opened, you will be able to add the project to the VSS database.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 7/27/2001 |
---|
Keywords: | kbBug kbDSupport kbinterop KB214607 |
---|
|