Connection strings and/or DB engines moving from Office2007 to 2010


Background: I'm running an ASP Classic website with Access 2007 databases. In the local site (which is now failing as per below) I'm under IIS7.5 and Windows Home Pro 7.

Having just upgraded from MSOffice 2007 to 2010, the database bits of my website - which called Access databases (all .mdbs) - have stopped working.

I believe this was because the Jet engine was dropped from Access after 2007, moving to Ace. I tried the following, without changing the format of the databases themselves (i.e. I left them as mdbs rather than accbs):

  1. I tried installing and using the 32 bit Ace engine which I got from The installation seemed to work - at least the install got listed under the control panel. I changed the connection string from:

"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\inetpub\wwwroot\mysite\databases\mydb.mdb;Persist Security Info=False"


"Provider=Microsoft.ACE.OLEDB.12.0;Data Source=c:\inetpub\wwwroot\mysite\databases\mydb.mdb;Persist Security Info=False"

[I have seen one source suggest Data Source is wrong and DBQ should be used. I tried that too.]

The error I got back was:

ADODB.Connection error '800a0e7a'
Provider cannot be found. It may not be properly installed.
/_RECAL/Includes/DBFns.asp, line 14 (the line on which I open the connection)

  1. Next I dropped the idea of using the 32 bit 2010 Ace engine, instead using this 2007 offering recommended by some:

I uninstalled the "old" database engine and installed the above.

I got exactly the same error message.

  1. Somewhat depressed I thought I'd give up; I'd install (additionally to MS Access 2010), MS Access 2007. That would get me the Jet engine back again. I uninstalled the the engine in 2) above and installed MS Access 2007 (and implicitly Jet). I did not uninstall MS Access 2010 although when I eventually tried to run MS Access 2010 it tried to run setup (because there was no Ace engine I guess).

But ... I still got the same error message.

I'm hoping someone can offer something better than uninstalling MS Office 2010 and reinstalling MS Office 2007.

0 answers