ACC: "Name Conflicts with Existing Module..." Error Message

Last reviewed: May 7, 1997
Article ID: Q137937
The information in this article applies to:
  • Microsoft Access versions 7.0, 97

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

When you try to convert a Microsoft Access 1.x or 2.0 database to Microsoft Access 7.0 or 97, the conversion process stops and you may receive the following error message:

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

CAUSE

A Microsoft Access object, such as a module, violates the naming conventions for objects, modules, and procedures in Visual Basic for Applications. For example, you have a module with the same name as a type library, such as "DAO," "Access," or "VBA."

RESOLUTION

Open the database in Microsoft Access version 1.x or 2.0 and rename the object.

This resolution assumes that you have Microsoft Access version 2.0 (or 1.x) installed on your computer. If you replaced version 2.0 (or 1.x) with 7.0 or 97 using the same folder on your computer, then you must re-install version 2.0 (or 1.x). You may want to re-install into a different folder so that you have both versions available for resolving the conversion problem.

REFERENCES

For more information about Conversion and Compatibility, search the Help Index for "converting databases," or ask the Microsoft Access 97 Office Assistant.


Keywords : CnvProb kberrmsg kbusage
Version : 7.0 97
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided


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.

Last reviewed: May 7, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.