Access 2010 - VBA: Name conflicts with existing module, project, or object library

Question

I was working with a new Access 2010 database and copied in VBA code from a 2003 database.  The code did not do what I anticipated and I realized that I did not select the reference "Microsoft DAO 3.6 Object Library".  I selected the reference, but received the error "Name conflicts with existing module, project, or object library".  I searched the Internet and nothing fixed this.  I then created a brand new database with nothing in it.  I created a module, immediately selected "Microsoft DAO 3.6 Object Library", and received the same message.  What is the issue?

Answer 1

Hi Bill

big thankyou for reply based on heaps more experience than I have.

And for taking the time out .

I did try compacting the database but this didn't solve the problem (on either machine).

I can't make it happen with two new forms open concurrently - must admit like most I'm tied to

deadlines and just want it to work....

As you rightly point out, my assessment of Access 2010 and 2013 really isn't worth a candle.

Words born out of frustration.  The better you know any apps development medium, the more you instinctively go with the strengths and work around the parts that need it.

I resorted to back to backups and rebuilt the database  - full steam ahead now.

Thankyou again

Jerry

Answer 2

Jerry - I'm glad I could be of assistance. When Access starts acting funny most of the time it's the database file itself. There are several ways to try to rescue bad files, but having backups is essential. There are a bunch of free utilities that let you back up as frequently as you like. I back up my development copies every hour and keep the last 15 backups.

One of the best, free backup utilities I've found is Karen's Replicator karenware.com

Answer 3

When compacting has failed to correct the problem, an easy fix to a bad file can be to simply make a new, empty, MDB or (not my favorite choice)  ACCDB and import all items from the old file.

Answer 4

When compacting has failed to correct the problem, an easy fix to a bad file can be to simply make a new, empty, MDB or (not my favorite choice)  ACCDB and import all items from the old file.

That's true. I suggest that on many occasions. The more design additions/changes you make without copious saves and compacting, the more chance you have of corruption.