FIX: Ambiguous Names Generate Incorrect Error MessageLast reviewed: December 18, 1997Article ID: Q171524 |
The information in this article applies to:
SYMPTOMSIf Binary Compatibility is set, then writing a duplicate Implements statement in a Class Module can cause a compatibility error to occur when compiling a DLL, instead of the expected "Ambiguous name detected" error message.
STATUSMicrosoft 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:
ARTICLE-ID: Q170365 TITLE : INFO: Visual Studio 97 Service Packs - What, Where,and WhyFor 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:
ARTICLE-ID: Q171554 TITLE : INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2 MORE INFORMATION
Steps to Reproduce BehaviorNOTE: MSO97.DLL is required to duplicate this scenario.
ResultThe following Visual Basic dialog box appears:
"The Class1 class implemented an interface in the version-compatible component, but not in the current project. If you choose Accept, the Class1 class module will no longer support client applications compiled against the version-compatible component. To avoid this incompatibility, add the interface declaration back into the class module, or clear the version compatibility setting in Project Options."The correct error message that should display is:
"Compile error: Ambiguous name detected: IFoundFiles"Note that this message does display after the initial dialog is dismissed. NOTE: This behavior has also been reported when duplicate Enum names are used. Keywords : vb5all VS97FixlistSP3 VS97FixlistSP2 VB5FixlistSP2 Version : 5.0 Platform : WINDOWS Issue type : kbbug Solution Type : kbfix kbservicepack |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |