Share via

64-bit ODBC drivers for Access (Office 2016)

Anonymous
2016-05-12T12:08:32+00:00

I’m running 64-bit Windows 7 Pro SP1.

I needed the 64-bit odbc drivers for Access databases and naturally thought that these would be installed if I upgraded from 32-bit Office 2010 to 64-bit Office 2016.

The process of making that upgrade has been a nightmare in its own right. (It has taken me the best part of a week). The Access version installed is 16.0.4266.1003 64-bit. Imagine my despair then to find that, having 64-bit Office 2016 installed, did not result in the 64-bit drivers being installed.

I therefore downloaded and tried to install the 64-bit Access 2016 runtime. And this is what happened…

We're sorry, Microsoft Office installer encountered a problem because you have these Click-to-Run installer based Office programs installed on your computer.

Microsoft Office Professional Plus 2016 - en-us

Windows Installer and Click-to-Run editions of Office programs don't get along for this version, so you can only have one type installed at a time. Please try installing the Click-to_run edition of Office instead, or uninstall your other Click-to-Run based Office programs and try this installation again.

So, I thought I’d try to install the 64-bit Access 2013 runtime, and this is what happened…

Microsoft Access Runtime 2013 encountered an error during setup.

So, just what am I supposed to do to get the 64-bit Access ODBC drivers installed????

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

8 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-09-07T03:52:34+00:00

    > MS could have designed both to install 32 and 64 bit applications in totally separate locations.

    That is exactly what is accomplished by my VM suggestion.

    Sorry, I beg to differ.

    Yes using a VM allows what appears to be this sort of installation, but it is not a simple solution.  It requires paying money for VM software, either a more expensive version of Windows, ie Pro, or a 3rd party program (yes there is freeware, but not for business use). And you have to buy a separate Windows license to install inside of the VM. And depending on your VM tool, and how it is setup, you may not be able to share information between applications in the native windows and VM.

    All in all, it would have been better if MS had designed Windows to totally isolate 32 and 64 bit application installations, allowing both types to be installed on the computer at the same time, but they didn't.  Don't bother to tell me it's not possible.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  2. Tom van Stiphout 40,201 Reputation points MVP Volunteer Moderator
    2016-05-12T13:50:44+00:00

    > I needed the 64-bit odbc drivers for Access databases

    Why?

    The best practice is to use the 32-bit MSI installation of Office, especially if you want to use other drivers or Automation.

    Some of us initially thought that CTR was just a more convenient way of buying Office and getting it on your machine. If MSFT had left it at that, great, but no, they had to drag in some virtual machine that Office now runs in which has the nasty side effect of no Automation with the rest of the world, and we now have these conflicts between MSI and CTR installations. From where I sit, it's not a pretty sight, but there you have it.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Tom van Stiphout 40,201 Reputation points MVP Volunteer Moderator
    2017-09-07T04:37:39+00:00

    > Don't bother to tell me it's not possible

    No I won't. Unproductive.

    I'm thinking a company of the caliber to have its "our own data-processing engine in 32 and 64 bit form" is probably not without any means and will probably have an MSDN subscription or some other way which includes some server OSes and some client OSes, so Hyper-V is included and can be used to setup the VMs I'm suggesting.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2017-09-07T03:17:43+00:00

    Yes, the simplest approach is to use a VM to totally isolate the installations. But that has its disadvantages too.

    The simple reality is that we can't mix 32 and 64 bit installations because MS was lazy when it designed Windows and Office installers. MS could have designed both to install 32 and 64 bit applications in totally separate locations. But they didn't.

    During the install, there is supposed to be a message showing which applications are in conflict. Of course sometimes that doesn't work.

    Try going into the Programs and Features dialog and locate any Microsoft applications. By default MS install 32 bit, so anything you find will most likely be 32 bit.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2017-09-07T00:24:23+00:00

    I am running with Windows 10 - 64 bit processor.

    I am trying to steup "accessruntime_4288-1001_x64_en-us.exe", get setup error, cant install due to finding 32 bit programs. how do I do it?

    Can't find how to fix clash of programs 64 vs 32 or 16.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments