FIX: Binary Compatibility Broken When Adding Events

• Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 5.0

SYMPTOMS

Adding Events to an ActiveX EXE Object whose instancing property is set to "PublicNotCreatable" may result in the following Binary Compatibility error:

The <Class Name> Class Implemented An Interface In The Version-Compatible Component, But Not In The Current Project.

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 Basic 6.0

MORE INFORMATION

Steps to Reproduce Behavior

1. Create a new ActiveX EXE project in Visual Basic 5.0. Class1 is created by default.



2. Set the Class1 instancing property to "2-PublicNotCreatable."



3. Add a new Class Module (Class2) to the project.



4. Select Make Project1.exe from the File menu.



5. Select Project1 Properties from the Project menu, then select the Component tab.



6. Select the Binary Compatibility option button under the Version Compatibility section. Project1.exe should automatically be shown in the textbox.



7. In the Class1 code window, add the following statement:

   
         Public Event MyEvent() 




8. Repeat step 6. Select "Yes" to overwrite the older file when asked. The following message will appear:

   The Class1 Class Implemented An Interface In The Version-Compatible Component, But Not In The Current Project.

Additional query words: kbDSupport kbActiveX kbVBp500bug kbVBp600fix kbVBp kbdss

Keywords : kbGrpVB
Version : WINDOWS:5.0
Platform : WINDOWS
Issue type : kbbug