Can Access 2010 Runtime 32-bit coexist with Office 2016 64-bit?
Is it possible to run an Access 2010 accde created with 32-bit access on a computer where Access 2016 64-bit is installed by using Access 2010 runtime in parallel? Can I install and call the 32-bit access runtime without messing up the 64-bit access 2016 install?
Thanks in advance!
Microsoft Access
Last Comment
Jim Dettman (EE MVE)
8/22/2022 - Mon
Daniel Pineault
Technically, yes. Different versions can coexist. You can then create a shortcut or script to launch the database using a specific msaccess.exe.
On the other hand, why not simply make the database 64-bit compliant?
Bill Ross
ASKER
Hi Daniel,
Thanks for the feedback.
Suppose our db is C:\Test\Test.accde what would be the Access 2010 command line?
Regarding 64-bit compliance - the issue is that we have a 32-bit custom ActiveX control that has no 64-bit version and it crashes on 64-bit Access. Now that MS Office defaults to 64-bit we are having issues. With Office 2016 and 2019 installing the 32-bit is not trivial as before.
If you cannot make the database 64-bit as you said, can you use Office 32-bit.
With Office 2016 and 2019 installing the 32-bit is not trivial as before.
I am using Office 2016 32-bit. You should be able to uninstall Office (including the V2013 components), restart, and install Office as 32-bit. See if that works.
Thomas Zucker-Scharff
I have installed O2010 aside O2016 previously, the only thing to be wary of is outlook, which should only have one version per device.
Bill Ross
ASKER
Hi Everyone,
Thanks for the various comments. I do not have control over which Office version the users install. My app (accde) has been in production for 10+ years in over 100 locations but uses 32-bit ActiveX controls that have no 64-bit version so I'm thinking of installing Access RunTime 32-bit to make sure it works. The current Office install now defaults to 64-bit so I'm having issues - thanks Microsoft...
The accde works OK on 2007 so based on Jim's posting, I'm going to fire up RunTime 2007 on my Office 2016 64-bit computer and see what happens. I'll let you know.
On the other hand, why not simply make the database 64-bit compliant?