Documentation on ACE drivers.

Question

_{Wednesday, January 13, 2016 12:06 PM}

Hi,
I am aware about ACE drivers are released after JET and can be used for 32 and 64 bit versions unline JET which can be used for 32 bit only.

Now I found that there are two releases of ACE

ACE.OLEDB.12 and ACE.OLEDB.14( for office 10 and 13) Please correct if I understood this wrong.

But my question is there is no documentation related to above two different versions.

I want to know what are the difference between both the version of ACE drivers.
As ACE.OLEDB.12 is working even with office 2016, will there be any driver release for office 16 also.

And what is the compatibility of the these versions of drivers with different versions of office.

So far I could not find any documentation or thread.

Please post your knowledge or if any link which can asnwer these.

A user friendly computer first requires a friendly user

All replies (7)

_{Thursday, January 14, 2016 2:18 AM ✅Answered | 1 vote}

Hi bahushekh,

>>I want to know what are the difference between both the version of ACE drivers.
As ACE.OLEDB.12 is working even with office 2016, will there be any driver release for office 16 also

Based on my understanding, all offices from 2007-2016 contain the provider Microsoft.ACE.Oledb.12.0. With the link below, you could get Access 2016 runtime.

#Access 2016 Runtime is now available for download
https://blogs.office.com/2015/12/16/access-2016-runtime-is-now-available-for-download/

>>what is the compatibility of the these versions of drivers with different versions of office

In my option, later versions of drivers would be compatibility with earlier version. I think you could distribute the Access runtime when you distribute your project in case the Access runtime did not installed at end client.

Best Regards,

Edward

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

_{Thursday, January 14, 2016 4:38 AM}

Thanks Edward,

Thanks for the reply. It contains helpful points and link for Access 2016 runtime is really what I needed for long time( As after multiple Google searches we have assumed that drivers release for access 16 is still pending :) )

"Based on my understanding, all offices from 2007-2016 contain the provider Microsoft.ACE.Oledb.12.0. "

You mean when I install any office from 2007-2016 it will install the provider Microsoft.ACE.Oledb.12.0. But when I externally install the access drivers from the links (eg as you have shared the drivers link for access 2016) it will install the upgraded version of drivers.

A user friendly computer first requires a friendly user

_{Thursday, January 14, 2016 5:58 AM}

Hi bahushekh,

Thanks for your test result. What I mean is that we could use provider Microsoft.ACE.Oledb.12.0 under all offices, but maybe I am incorrect. I think you could try to use Microsoft.ACE.Oledb.12.0 with Access 2016 runtime installed to check.

With installing office or access runtime, I think it would install corresponding provider, and your test result is expected behavior.

If your issue has been resolved, I suggest you mark the helpful reply as answer to close this thread.

Best Regards,

Edward

_{Thursday, January 14, 2016 6:37 AM}

Thanks for the reply again.

I have checked after installing Office 2010 runtime and it installs ACE.OLEDB.12 provider. And I can use these drivers with Office 2016 also without any problem(tested)

I again checked after installing Office 2013 and it installed ACE.OLEDB.12 and 15.

I cant check with 2016 runtime as I have C2R office 2016 installed on my machine so will share the results in future.

Thanks for clearing doubts.

A user friendly computer first requires a friendly user

_{Monday, May 16, 2016 6:47 PM}

Hi Edward,

I don't think ACE 12.0 works with Access Runtime 2016 installed.

I have both a C# application and some VBA code in Word that both work fine if Access Runtime 2007 or 2013 is installed but do not work when Runtime 2016 is installed.

Also I seem unable to install Access Database Engine 2010 and Access Runtime 2016 side by side.

Can you advise how I can get by code to run again with Access Runtime 2016 installed?

The connection string is:Provider=Microsoft.ACE.OLEDB.12.0;" _
+ "Data Source=\blahblah.accdb;Jet OLEDB:Database "

_{Tuesday, May 17, 2016 1:31 AM}

Hi Edward,

I don't think ACE 12.0 works with Access Runtime 2016 installed.

I have both a C# application and some VBA code in Word that both work fine if Access Runtime 2007 or 2013 is installed but do not work when Runtime 2016 is installed.

Also I seem unable to install Access Database Engine 2010 and Access Runtime 2016 side by side.

Can you advise how I can get by code to run again with Access Runtime 2016 installed?

The connection string is:Provider=Microsoft.ACE.OLEDB.12.0;" _
+ "Data Source=\blahblah.accdb;Jet OLEDB:Database "

Hi LuckyLuke,

For your own issue, I would suggest you post a new thread and share us more information.

>> I seem unable to install Access Database Engine 2010 and Access Runtime 2016 side by side.

Did you get any error when you install Access database engine 2010 and Access Runtime 2016 side by side? The link below might be useful to you:

# Connection String Access 2016

http://answers.microsoft.com/en-us/office/forum/office_2016-access/connection-string-access-2016/896ba075-7fcd-4be8-9f44-ec514b01cc11?auth=1

Best Regards,

Edward

_{Tuesday, May 17, 2016 9:11 AM}

Hi Edward,

Thank you for your reply. I had seen the post you referenced but it didn't help me.

As suggested I have started a new thread with a more comprehensive description here:

Problem opening OLEDB from PC with Access RunTime 2016

Hopefully this gives you enough info to understand the cause of the problem.

Kind Regards

Luke

Last updated on 2016-01-13

Share via

Documentation on ACE drivers.

Question

All replies (7)

Additional resources