DOCUMENT:Q186262  16-JUN-1998  [vbwin]
TITLE   :BUG: Name Conflict When Using Binary Compatibility
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:5.0,97sp3
OPER/SYS:WINDOWS
KEYWORDS:kbVBp500bug

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Visual Basic Professional and Enterprise Editions for
   Windows, version 5.0
 - Microsoft Visual Studio 97sp3
---------------------------------------------------------------------

SYMPTOMS
========

When compiling a project in Visual Basic with binary compatibility, you
receive the following error:

   "Name conflicts with existing module, project or object library."

However, you have not made any change that would warrant such an error.

CAUSE
=====

This is a bug in the Visual Studio Service Pack 3 version of VBA5.DLL for
Visual Basic 5.0. The error typically occurs only after compiling several
generations of a component with binary compatibility.

RESOLUTION
==========

Turn off binary compatibility.

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: kbVBp500bug kbDSupport kbdss kbVS97sp3bug kbVBp500
======================================================================
Keywords          : kbVBp500bug
Version           : WINDOWS:5.0,97sp3
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbpending

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1998.