The information in this article applies to:
SYMPTOMSWhen developing an ActiveX DLL or ActiveX EXE, Visual Basic might erroneously report that you have broken Binary Compatibility when you try to compile your project. This could happen even if you have not changed a single line of code in your project. CAUSE
The most common cause for this problem is a known bug, in which ENUMS is
used as a function parameter.
When you try to compile this code with Binary Compatibility turned on, you
might receive the following error:
When you receive the error, you can click the "Show Declaration" command button (which shows you the version-compatible declaration of the function and the declaraton in the current project). Note that the two declarations are exactly the same, even though Visual Basic gives the error. Service Pack 3 for Microsoft Visual Studio addresses this issue, but does not always fix the bug. For additional information, please see the following article in the Microsoft Knowledge Base: Q171819 FIX: Invalid Enum Value Causes Incompatible Binary Compatible RESOLUTIONThe following are three suggested workarounds for this bug:
Steps to Implement the Type Library WorkaroundThe Binary Compatibility bug usually occurs with very large projects, and late in development. However, if you do start receiving broken Binary Compatibility error messages, you should do the following:
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. Additional query words: kbDSupport kbdss vb6test
Keywords : kbVBp500bug kbGrpVB |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |