DOCUMENT:Q190200  07-AUG-1998  [vbwin]
TITLE   :BUG: Name Conflict Error Even After Renaming Module
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:5.0
OPER/SYS:WINDOWS
KEYWORDS:

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

 - Microsoft Visual Basic Learning, Professional, and Enterprise Editions
   for Windows, versions 5.0, 6.0
 ---------------------------------------------------------------------

SYMPTOMS
========

In a Microsoft Visual Basic project, when you give the same name to an Enum
and a class module and run the project, you will get the following error:

   Compile error: Name conflicts with existing module, project or
   object library

However, after you resolve the name conflict by changing the name of the
class module, the same error still occurs when you run the project.

CAUSE
=====

Visual Basic does not rebuild the binding table upon the name change.
Therefore, the change is not reflected in the system and the conflict
persists.

RESOLUTION
==========

You need to make a few changes to the project (for example, add some code
to the modules) or reload the project to workaround this error.

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.

MORE INFORMATION
================

Steps to Reproduce Behavior
---------------------------

1. Open a new ActiveX DLL project in Visual Basic. Class1 is created by
   default.

2. Paste the following code into the code window of Class1:

      Public Enum t1
         red
      End Enum

3. Select Add Class Module from the Project menu and add another class
   module to the current project.

4. Rename Class2 to t1 using the Properties window.

5. Press the F5 key to run the project. The following error will occur:

      Compile error: Name conflicts with existing module, project or
      object library

6. Rename the class module t1 back to Class2.

7. Press the F5 key to run the project again. Note that the same error
   message still occurs despite the fact that the names are no longer in
   conflict.

Additional query words: kbDSupport kbdss kbVBp500bug kbVBp600bug kbVBp
kbCompiler
======================================================================
Version           : WINDOWS:5.0
Platform          : WINDOWS
Issue type        : kbbug

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

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.