'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine solution

'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine solution

Solution 2:

Download 2007 Office System Driver: Data Connectivity Components from here:

Direct Download:

Solution 3:

Download Microsoft Access Database Engine 2010 Redistributable from here:

Personally Solution 2 works for me.

Do not forget to leave your comments below to inform me whether it works. Thanks. :-)

Feel free to visit my blogs:

[brianbrewster]

Man - you are a LIFE SAVER!! I was super frustrated by wanting to link a database with my VS project and so far no matter what I did I ran into problems. You think the engineers at Microsoft would look into these matters and issue an update (SP2 for instance) that fixed all these pesky problems. And SOLUTION #2 seemed only one that fixed this problem. That you very very much!

[stevezct]

step 2 works for me. im using vs 2012 and ms office 2016. thank you so much . i love you man

[Whrse]

32bit Visual Studio 2013 + 64bit Access 2013 here (on a 64bit Windows 8.1 system) and all I needed was the second solution to make it work. Thanks!

[danielavallejo]

The Solution 2 worked perfectly for me. Visual Studio 2015 and Access 2016. Thank you so much!

[masyitahmustapha]

Solution number two helped me! once u have downloaded the file, try to close your application then open it again. and try to run ur program. surely it works!

[ronchedowboon]

Thanks Mei Yi, I am using VS2013 Professional and MSOFFICE 2007. Got this message Access Violation!!! on NET Framework4. On NET Framework 3.5, I have the same message "Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine"  After I try your method, It works fine!!! thanks again.

[egilryengen]

Hei Mei Yi
I see you have help others. I do have the same problem. However I am running Office 2013 and Access 2013. I first installed the official version of the OLEDB.12.8. After that I installed Solution 2 as recommended with no luck.What to do?
Regards Egil

[xrdang]

Solution #2 worked for me, not solution #1. I greatly appreciate that you posted this information, it made my job much easier. I am writing a C# program using VS 2015 hitting an Access 2010 (accdb) database. I would not have thought of going backward to a 2007 download. Thanks again.

[randysandberg]

Thank you. The second solution helped me. I was bothered by this for a long time. Can't understand how Microsoft would leave this "hole" in one of their products.

[kaightaylor]

Thanks, I am running VS Pro 2015 and Access 2016 and solution 2 worked fine!

[kenanserran]

Solution 2 worked like a charm. i couldn't get my application that i was testing out that i created years ago. i don't even have Visual Studio on PC lol. lots of thanks to you

[GrEzzTROL]

autor of this video is THE best HUMAN on all planet

[josonmorales]

Thank you so much! This really helped me. I still had the same issues despite installing the database 2010 driver and solution 2 was all I really needed. I hope you have a blessed life and Godbless

[danievanstryp]

I have Office 365 64-bit and Visual Studios 2019 on my 64-bit operating system. Non of the solutions work for me. Any help

[mukeshlekhrajani]

After Searching 15+ Websites On The Internet. It Was This Video That Helped Me To Get Connected To MS Access 2013 (ACCDB) Through VB .Net.


Mei Yi Tan = KEEP UP THE GOOD JOB.

[LordsiVR]

LIFE SAVER Solution 2 worked for me even for 2016

[shwetaagarwal]

i m using microsoft access 2007 and microsoft visual studio 2008 express edition... i m getting the error : The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine

[thegraybeyatris]

Hi Sir! Uhm, I can see you really do help a lot of people by sharing your knowledge. I'm not here to ask you anything or what, I just wanna give you my sincere thanks for being so generous of what you know in these areas. So for helping a lot of people, I sincerely thank you Sir. Not all people are like you, so please keep it all up! Two thumbs up!

[dumaciel]

The 2nd solution worked perfectly! VS2013 + Office 2010. Thank you so much!

[waelelsherif]

Thanks so much. I m using VS 2015 and Office 2016, solution 2 worked