Microsoft KB Archive/171531
Article ID: 171531
Article Last Modified on 12/10/2003
- Microsoft Visual Basic 5.0 Control Creation Edition
- Microsoft Visual Basic 5.0 Learning Edition
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
This article was previously published under Q171531
When building an ActiveX control project with "Binary Version Compatibility," Visual Basic may cause the following error:
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:
170365 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:
171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2
This behavior will only occur if a previous build of the ActiveX control is canceled due to an incompatibility warning and then a subsequent build of the ActiveX control is started.
Steps to Reproduce Behavior
- Start a new ActiveX Control project in Visual Basic 5.0.
- From the View menu, select Code.
Enter the following code in the General Declarations section of UserControl1:
Event Goo() Public Boo
- Select Make Project1.ocx from the File menu, and click OK.
- Open the Project Properties dialog from the Project Menu.
- Select the Component Tab, and click Binary Compatibility.
- Select the General Tab and change the Project name to Project2. Click OK.
- (Important!!) Press CTRL+J in the UserControl1 Code window to invoke the list of properties/methods. (A recompile is forced this way.)
- Make the Project1.ocx again from the File Menu. Click OK.
- Answer Yes to overwrite project1.ocx. When you get a warning about the name property being different, choose Accept.
- Select Cancel from the incompatibility warning dialog.
- Select Cancel Again from the make project dialog.
- Choose Make Project1.ocx again from the File Menu. Select OK.
- Answer Yes to overwrite project1.ocx.
Visual Basic will cause a Invalid Page Fault in <module> at <address>.
Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171531