BUG: New Implements Does Not Generate Incompatibility Error
Article ID: 190492
Article Last Modified on 5/13/2003
APPLIES TO
- Microsoft Visual Basic 6.0 Learning Edition
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual Basic 6.0 Enterprise Edition
This article was previously published under Q190492
SYMPTOMS
If you remove a Public data member and add an Implements statement with the
same class name as the removed Public data member and with Binary
Compatibility set, Visual Basic does not generate a compatibility error as
expected.
Existing client applications using the data member may generate a fatal
error (GPF) with the new compatible server.
RESOLUTION
If you comment out Public data members, ensure you are not using the same
identifier name in an Implements statement.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. We are researching this bug and will post
new information here in the Microsoft Knowledge Base as it becomes
available.
Additional query words: kbdss kbDSupport kbVBp kbVBp600bug kbCompiler
Keywords: kbbug KB190492