FIX: ReComputeRepository GPFs if Passed Non-existent DB Name

 Last reviewed: December 18, 1997
Article ID: Q169306
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

ReComputeRepository GPF's if passed a non-existent DB Name.

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

Pass the ReComputeRepository a database name that doesn't exist. For example: 

   lRtn = ReComputeRepository("c:\temp\invalid.mdb", "", "")
Expected:
  • No GPF.

Results:
  • First Dialog: "Failed to open database". Second Dialog: "Failure:hr=0x80041013" Third Dialog: "Error: The database "xxx.mdb" was not found." Fourth Dialog: "The instruction at "0x019201a0" referenced memory at "0za0019201". The memory could not be "read". 
Keywords          : 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.