Missing/misplaced reference dlls

[steveg242]

[SOLVED]Missing/misplaced reference dlls

I've done a search but only got bits and pieces of what might be a solution, so…

I got a new computer with win7 and Access 2010 (had XP with 2003)

I am having a hard time opening some of my databases. It seems to be a reference issue. I want to reference Microsoft DAO 3.6 Object Library but when I do it says "Error in loading DLL" the path it gives is: C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll

I found the DLL in C:\Program Files (x86)\Common Files\microsoft shared\DAO

There is a browse button, but when I go to the correct file and select, I still get the "Error in loading DLL" file.

Anyone else encounter this? Is there a quick solution? Will it be sufficient just to move all the dlls in Program Files (x86) to Program Files? Or at least copy them?

I'm going to lunch now and will give this a try when I get back (with the proper backups of course). But I wanted to see if anyone can quickly give a better solution. I got my comp on Monday…it's Wednesday and I still don't have my dev environment up and running. Gotta love upgrades.

 

[jdraw]

From Hans V

The Microsoft DAO 3.6 Object Library is for .mdb databases only.

The equivalent for .accdb databases in Access 2010 is the Microsoft Office 14.0 Access database engine Object Library. You probably already have a reference to this library.

In your code, you refer to this library as DAO, so "old" code such as



Dim rst As DAO.Recordset



will work without having to be modified.

 

[steveg242]

Ok, thanks. It is an mdb database.
I know it's probably high time to convert that to .accdb but that's another project.

 

[pr2-eugin]

Was this working properly before you moved to a different computer? Or is it still working on some other computer with similar configuration?

 

[steveg242]

Yep, everything was working fine. This is the first time I've opened the .mdb file in anything other than Access 2003.

edit: Ok, this time I open it (about the 20th time) and everything seems to be working fine. :banghead:

Perhaps it wasn't the references afterall. I was focusing on that because of those error messages.

Thanks for your help guys. But as I go through things, I'm sure I'll encounter some other issues. I never expected the transition from 2003 to 2010 to be seamless.