I want to do a hand install of the MS Access 64 bit odbc drivers. Uninstalling 32 bit Office and installing 64 bit Office is not an option due to the add-ins that our compa
I have managed to install both without side effects on Office installation and without using /passive option. Downside is that is tested and working only on one Office version for now. Microsoft.ACE.OLEDB.12.0 driver for x64 app - how to make it work with x86 MS Office installed?
I ran into this same issue with a SpringJDBC app that connected to an access DB when I ported it over to a win7x64 box running eclipse-4.3x64 Kepler.
What ended up working for me was to COMPLETELY remove 32bit Office2010 [ and Lync and other MS apps tied to this ] and install the 64bit versions.
Here's the really fun part: The driver name to which you use for Access64bit driver name is now:
|Microsoft Access Driver (*.mdb, *.accdb)|
Yes, that's a comma-space after "mdb".
So, my spring-config for the Datasource looks like:
<bean id="dataSource"
class="org.springframework.jdbc.datasource.DriverManagerDataSource"
lazy-init="default"
autowire="default"
dependency-check="default">
<property name="driverClassName"
value="sun.jdbc.odbc.JdbcOdbcDriver"/>
<property name="url"
value="jdbc:odbc:;DRIVER=Microsoft Access Driver (*.mdb, *.accdb);DBQ=/Data/dbs/cl97_2k.mdb;"/>
<!-- Above is Access 64bit Driver Reference -->
<!-- Below is the Access 32bit Driver Reference.
value="jdbc:odbc:;DRIVER=Microsoft Access Driver (*.mdb);DBQ=/Data/dbs/cl97_2k.mdb;"/>
-->
<property name="username" value=""/>
<property name="password" value=""/>
</bean>
Hope this Helps!
using the /passive switch you can install 64-bit ace drivers even if 32-bit ms office is present: http://blog.codefluententities.com/2011/01/20/microsoft-access-database-engine-2010-redistributable/
Just be warned that installing the 2010 64-bit ACE engine on a machine with 2010 32-bit Office already installed CAN lead to some wacky behavior in your already existing Office 2010.
To install the Microsoft Access 2016 ODBC Driver, run the installer from the command line with the /quiet
switch (which replaces the /passive
switch from previous versions).
You'll also need to delete or rename the mso.dll registry value in the following registry key:
This information collected from the Data Savvy blog.