FIX: Statement Builder Crashes Referencing GlobalMultiUse Server

• 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:

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

Q171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2

MORE INFORMATION

Steps to Reproduce Behavior

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



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

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

   NOTE: The exact function is not important. This error may also occur with Property Let and Property Get statements.



3. Change the Instancing property of Class1 to 6 - GlobalMultiUse.



4. Save Project1.



5. Go to File | Add Project to add a Standard EXE (Project2) to the project group.



6. From Project2, go to Project | References, to reference Project1 by clicking on its check box.



7. In the Form_Load event procedure of Form1, type Project1.test, and then hit the space key. An application error should occur.

Additional query words:

Keywords : kbVBp500 kbVS97sp2fix kbGrpVB kbvbp500sp2fix
Version : 5.0
Platform : WINDOWS
Issue type : kbbug