Can i use 32 bit asap on office 2016 64 bit

#CAN I USE 32 BIT ASAP ON OFFICE 2016 64 BIT INSTALL#

Is there any reasonable way to make this work? Both are being installed, but once on the system either our software no longer works, or Office constantly repairs its installation.

So, has anybody managed to find a way to make the 32-bit drivers coexist with 64-bit installations? I have seen that installing with /passive flag allows the two to be installed, and our installer does use passive. Either our software breaks, or their software breaks.

#CAN I USE 32 BIT ASAP ON OFFICE 2016 64 BIT INSTALL#

A further issue is that non-legacy software will sometimes install the 64-bit drivers (as they should), and the two versions simply do not coexist in any reasonable manner. Either the 64-bit Office breaks our installation, or our installation breaks their Office version, but it's not pretty either way. As computers come off the assembly line with 64-bit versions installed, we're unable to keep up with support requests when our software breaks something. Trust me, we've tried to educate users that 64-bit Office is largely unnecessary, to no avail. However, the problem begins when Office 2010 64-bit is installed on the system. Indeed, when we install 32-bit drivers on a 64-bit machine, and run our 32-bit applications, it works correctly. So, we are under the assumption that the driver must also be installed as 32-bit.

Our software deals with a lot of legacy components that are 32-bit, and much of it is in VB6 code, which generates 32-bit assembly. However, apparently you need to always install the 32-bit version if the host process is always 32-bit. The engine comes in 64-bit and 32-bit forms, which is good. We currently have a major issue using Microsoft Access Database Engine 2010.

Can i use 32 bit asap on office 2016 64 bit