2007 runtime dll problems

[suepowell]

Hi
I have developed a database in access 2007, originally in 2003 format and
deployed it using runtime on XP pc's. This works fine.

I have converted the format to. accdb, recreated the deployment package and installed this again on the same PC's, and one that did not have the original version. In all cases the new version of the database returns the error
"missing msado15.dll with access 2007 runtime"

and the program will not run.

Can anyone help with this problem, I have this installed on quite a few PC's
so I am looking for a solution I can put in the install package if possible,
rather then having to go to each PC to change it's settings.
Most of these PC's didn't have a previous version of access, but they all
have a version of office installed.

I have asked this question on the microsoft forums to no avail, so I am relying on this forum to sort out the problem, you very rarely let me down so I'm sure someonw out there will be able to help.

thanks for your help.

Sue

 

[DJkarl]

This sounds like a missing reference issue. I believe that DLL is used for ADO connections. If you have something in your code like this

Dim cn as ADODB.Connection
Set cn = New ADODB.Connection

You might want to move to something more like this

Dim cn as Object
Set cn = CreateObject("ADODB.Connection")

This way Access will use whatever DLL is available and you will be less likely to get reference related errors.

 

[suepowell]

Hi,

Thanks for the reply.

I have tried making the changes you suggest in all the modules of my database.
I have tried running the modified database on the already installed version of runtime, this didn't work so I uninstalled the database and access runtime and ran the install package created from the modified version of the database. Again it didn't work.

Has anyone any more ideas, this is really holding up the deployment of a system that is otherwise ready to go and urgently wanted.

Thanks

Sue

 

[DJkarl]

Have you checked out this link from MS yet?

http://support.microsoft.com/kb/317388

 

[suepowell]

HI,

Thanks DJKarl, I checked the link but it didn't help.

I thought I would post the answer to save others the trouble I have had with this.

My problems stemed from the fact I was using Activex Data Objects 6.0 on the Vista PC. I presume it comes with Vista not Access 2007 or runtime.

I couldn't get this onto the XP PC, even if I tried to download it from the Microsoft site. And if I copied it from the Vista PC it wouldn't register.

If I changed the reference back to version 2.8 it wouldn't even run on the Vista PC.

The solution is to use the 2.8 version, but to move the reference higher on the list than then the Microsoft Office 12 Access Databse Object Library reference.

I had seen something on this site about order of references, and this is what gave me the clue to solving the problem.

I have been using ADO for years, since Access 2000 in fact, I thought I was moving wth the times, so am surprised to find DAO is now default.

Once I had the correct reference the runtime worked fine.

Good luck with runtime, It's a really useful tool and easy to deploy.

Sue

 

[DJkarl]

Thanks for posting your solution, good to know.