Name conflicts with existing module, project...

[jema53]

When I go to Tools>References in VBA and try choosing Microsoft DAO 3.6 Object library, I get the following message: "Name conflicts with existing module, project, or object library". When I hit Access help, it tells me that:

1. There is already a module, project, or object library with this name referenced in this project, or
2. You attempted to add a reference to a project or object library whose file name (without an extension) is the same as the name of one of the current project's modules.

This has me mesmerized because neither my module (module1), nor my project, nor the object library has any name that should conflict with adding this library and to use DAO I need this reference. Any ideas why this is happening? Thanks for your help.

[jimatqsi]

Check this out: http://office.microsoft.com/en-us/vi...080353798.aspx

You attempted to add a reference to a project or object library whose file name (without an extension) is the same as the name of one of the current project's modules. Change either the module name or the name of the file that could not be added.

I don't think it matters what the names of your modules are (except for class modules). You could most likely just change the name of the conflicting module and never miss a beat. Note that when you click on the reference you want, the path and name of the file is shown elsewhere in that window. That should point you immediately to the problem module name.

Jim

[zmbd]

ABSOLUTELY DO NOT CHANGE THE NAME OF A REFERENCE LIBRARY FILE!
This is bogus advice from MicroSoft

Doing so will more than likely break any other program referring to that library and may also result in other programs within the Office suite you are using to malfunction as well.

One of my fellow employees working on a project ran into this same error several years ago, and did just that on his PC because he didn't want to change the module name. Locked him out of Access, Excel, the Sharepoint server, the ODBC connection to the SQL-Server wouldn't authenticate to the Access Front end once we named the file back to the original. In short, we ended up having IT-Support wipe his drive and re-image from the enterprise master (thankfully, the server makes backups of the work document directories!)