Jeff Moden wrote:
To be honest, I've never needed the 32 bit version and so I've never tried to install it in parallel with the 64 bit version. That being said, you've piqued my curiosity... have you actually run into a situation where the 64 bit version failed to do something where the 32 bit version did not?
Like I said... not a challenge... just being curious about something I've never done.
a common situation to require 32 bit AND 64bit is for developers of SSIS.
Visual Studio is a 32 bit environment - so while developing you NEED the 32 bit version of all the drivers.
but while debugging developers most of the times do it in 64 bit - so it would also require a 64 bit of the driver.
add this to the fact that in many companies (or even on a per user basis) the Office install is 64 bit - if you are a developer with such an install, trying to install the 32 bit version would fail.
newer versions of office (click to play) make this even worst as they do not allow 32vs64 bit at all, neither does the base office install on this case expose the require drivers for other applications to use (they are there but only available to office applications to use)
so for a developer one would need to
- install ACE runtime 2010 32 bit
- install ACE runtime 2013 64 bit with /passive switch
in order to allow both version of the driver to be installed (and this is an issue as 2010 version has "support and vulnerabilities" issues)