![microsoft access database engine 2003 redistributable microsoft access database engine 2003 redistributable](https://imag.malavida.com/mvimgbig/download-fs/microsoft-access-8534-9.jpg)
I execute the below test on my Windows 7 SP1 + Office 2013, using a Database2016. compatible)ĭownload Microsoft Access Database Engine 2010 Redistributable from Official Microsoft Download Centerĭoesn't matter if Access 2016 is alread installed, you must install it. or install 2010 (both setup 32/64 bit - SP2) version (Windows XP SP3 min. compatible).ĭownload 2007 Office System Driver: Data Connectivity Components from Official Microsoft Download Center Therefore you can install 2007 (32bit setup only) version (Windows XP min. accdb (2007-2016) is compatible with all versions (see image below captured from MSAccess 2016) and you just install in 'another machine' the Provider ACE and nothing else. I installed access 2016, again the vb application didn't work. To try once again, I have made one Hyper-V machine and installed Win7 with service pack1 and installed access 2016 run time. However Access 2016 is already installed there.Ģ. After packaging it to another machine of win 10, the database is not getting connected. I developed vb6 application using this provider on my win 10 machine. To install this download: Download the file by clicking the Download button and saving the file to your hard disk. I have tried your solutions but it didn't work. Note: Before installing this download, you must first remove any previous versions of the Access Database Engine from your computer by using Add/Remove Programs in the Control Panel. Thanks Delittante & Gibra for responding. If you are actually using ACE 12.0 you can probably just ignore the fact that MS Access 2016 is installed at all, and deploy the ACE 12.0 Provider with your program. But that isn't what you claimed in post #1 above, you said you were using MS Access 2016, which implies ACE 16.0 instead. If your program is requesting the ACE 12.0 Provider and you haven't installed it, then of course you will get that error 3706. Whether that can coexist in a machine where MS Access 2016 has been installed I couldn't say. ACCDB files then you want to install and work against the ACE 12.0 Provider. In any case if you are using ACE 12.0 format. I can't find anywhere that ACE OLEDB Engine Type values are documented. But this does not occur by magic, you have to specify the engine type when you create the database. Access 2016 and the ACE 16.0 Provider should be able to create and use 12.0 format files. There should be backward compatibility, i.e. ACCDB formats you have to stay in sync, there is no stability and no upward compatibility. The ACE 12.0 provider may not work with ACE 16.0 format.