FIX: Statement Builder Crashes Referencing GlobalMultiUse Server

Last reviewed: December 18, 1997
Article ID: Q171833

The information in this article applies to:

Microsoft Visual Basic Control Creation, Learning, Professional, and Enterprise Editions for Windows, version 5.0

SYMPTOMS

When referencing a function contained in a project that has its instancing property set to GlobalMultiUse, the Statement Builder may crash with the one of the following Application Error in VB5.EXE:

   "The instruction at <address> referenced memory at <address>. The memory
   could not be "read"."

 -or-

   "VB5 caused an invalid page fault in module VBA5.DLL at <address>"

STATUS

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

For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

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

For a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q171554
   TITLE     : INFO: Visual Basic 5.0 Fixes in Visual Studio 97
               Service Pack 2

MORE INFORMATION

Steps to Reproduce Behavior

Create a new ActiveX DLL project (Project1). Class1 is created by default.

Paste the following code in the General Declarations section of Class1:

      Public Function Test(a,b)
         Test = 3
      End Function

      (Note that the exact function is not important. This error may also
      occur with Property Let and Property Get statements.)

Change the Instancing property of Class1 to 6 - GlobalMultiUse.
Save Project1.
Go to File | Add Project to add a Standard EXE (Project2) to the project group.
From Project2, go to Project | References, to reference Project1 by clicking on its check box.
In the Form_Load event procedure of Form1, type "Project1.test" (without quotes), and then hit the space key. An application error should occur.

Keywords          : vb5all VS97FixlistSP3 VS97FixlistSP2 VB5FixlistSP2
Version           : 5.0
Platform          : 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.