FIX: Changing Obj Name Before Saving Results in Repository Error

 Last reviewed: December 18, 1997
Article ID: Q169332
The information in this article applies to:
  • Microsoft Visual Studio 97
  • Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, version 5.0

SYMPTOMS

Attempting to change the object name of a Visual Basic Project prior to saving results in the following error: 

  "An error occurred setting the name of a Microsoft Repository object.
  Error code 80041302 The Microsoft Repository for Visual Basic is shutting
  down"

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This has been fixed with Visual Studio Service Pack 1.

For additional information about the Visual Studio 97 Service Pack 1, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q170365
   TITLE     : INFO: Visual Studio 97 Service Packs - What, Where, and Why

MORE INFORMATION

Steps to Reproduce Problem

  1. Delete the repository.mdb.

  2. Start a new Standard EXE project.

  3. Select the project file in the Project Explorer window.

  4. In the Properties window, change the name to a DBCS name.

  5. Save the project and add to Source code control.(Adding to SCC may or may not contribute to the described behavior.)

Results:
  • Repository error: An error occurred setting the name of a Microsoft Repository object. Error code 80041302 Microsoft Repository Add-In for Visual Basic is shutting down. 
Keywords          : kberrmsg VS97FixlistSP2 VS97FixlistSP1 VB5FixlistSP2 vb5all VB5FixlistSP1 VS97FixlistSP3
Version           : 5.0 97
Platform          : NT WINDOWS
Issue type        : kbbug
Solution Type     : kbfix kbservicepack

================================================================================

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: December 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.