[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1964
  • Last Modified:

Database contains a missing or broken reference to the file "ACEDAO.DLL' version 12.0

I encountered this error when I upgraded my office computer to Access 2010.  Apparently I made a small change to the database that I use for client accounting and billing.  I developed this database many years ago In a prior version of Access and I am no longer familiar with programming.  My secretary has Access 2003, and when she attempted to open a replica of the billing database she received the above error.  I copied acedao.dll from my computer and placed it in a subdirectory on her computer.  In Access 2003 I referenced the Microsoft Access 14.0 Object Library, and the database runs.
Unfortunately when I close Access 2003 and reopen the database, the 14.0 Object Library appears as "MISSING" again.  How can I register it permanently?
0
AL-HB
Asked:
AL-HB
  • 5
  • 4
1 Solution
 
peter57rCommented:
You cannot use dlls from later versions of Access in earlier versions.

You have to fix the database in A2003 by setting the correct references for A2003.
You will need DAO3.6 instead of ACE.

Use Debug>Compile to check things are OK.
You should not make any further changes to the application design using A2010.  Do your changes using A2003.
Otherwise you risk not being able to open the database at all in A2003.

0
 
AL-HBAuthor Commented:
I tried adding DAO3.6 in the references, and it did allow the database to open and operate correctly. When I closed the database and reopened it I had the same problem – The reference to DAO 3.6 was gone and the reference again showed "MISSING Microsoft Access 14.0 Object Library."  
Can you give me more specific instructions for the use of Debug>Compile?  
Again, I guess I need to know how to permanently register the proper reference to DAO3.6.
Any help would be much appreciated.
0
 
peter57rCommented:
There is no 'permanent' registration.
Access updates its own references from older to newer versions but not from newer to older.  

You need to deselect anything marked as missing and select the correct library.  Access 12 is the one you need for A2003.

Debug>Compile is just a menu selection in the VBA scrren.
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
AL-HBAuthor Commented:
"When I closed the database and reopened it I had the same problem – The reference to DAO 3.6 was gone and the reference again showed "MISSING Microsoft Access 14.0 Object Library." "

Thanks, but I need the above to be addressed to solve the problem...  Any one?

I should add that the database has been saved in the Access 2003 format.  One would think that by choosing a prior format it would be usable by that version!
0
 
MzLiberty22Commented:
Create a new database using Access 2003 and import the contents. If you have multiple versions of Access on your computer, you can never open the database in a later version or it will get the missing reference.
0
 
peter57rCommented:
If you have deselected the missing references and then selected the correct ones - with the database open in A2003 - then you should NOT get a recurrence of the missing reference issue.

Following the advice given by MzLiberty22 should automatically give you the correct references.  But you must do this in A2003, not A2010.
0
 
AL-HBAuthor Commented:
If you have deselected the missing references and then selected the correct ones - with the database open in A2003 - then you should NOT get a recurrence of the missing reference issue.

... and yet I DO get a recurrence of the missing reference issue.

I guess what I will do is just upgrade all users to Access 2010.  I was reluctant to do that in the beginning because I wanted to continue to use the conflict viewer in Access 2003.  I do not understand why Microsoft would eliminate that feature in Access 2010.
0
 
peter57rCommented:
Sorry - just realised the significance of what you said in your first post.  Replication is so little used that I did not realise you meant it literally. I just thought you were referring to a copy.

You cannot make design changes in a replica. Full stop.

Is there any reason why you have used replication rather than just having both of you linking to the same backend file?
 
0
 
AL-HBAuthor Commented:
I solved this problem by upgrading all users to Access 2010.
I do use replication and data synchronization in order to preserve the integrity of the design master.
0
 
AL-HBAuthor Commented:
The "experts" failed to fully comprehend my question.  My own solution involved doing something I did not want to do – upgrade all users to Access 2010.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now