Create ACE Engine Redistributable for Access 2016!
Since Office Click-to-Run Installs can result in the ODBC / OLE-DB Drivers for ACE NOT being visible to the system outside of the VDI install environment, we need a CURRENT version of the ACE engine redistributable package (the last one being from Access 2010 - 6 YEARS AGO!)
For more info see: https://support.microsoft.com/en-us/kb/2874601
Microsoft now has a Click2Run Office 365-based redistributable out, but it's basically useless since interop-based programs can't se it.
Gareth Horton commented
Hi Mark, I completely agree, we are still having to ship the Office 2010 version with our product and do very complex detection routines to make sure we lay down the component when we need it and leverage locally available components if they exist.
However, we have found various issues with using 2016 (ACE OleDB) and are in the process of trying to figure out workarounds.
Most likely related to this:
We are still investigating.
Mark Burns commented
@Frank - you misunderstand the issue.
If you boy an o365 version that DOEs have Access...
but you select the Click-to-Run deployment installer, then oafer O365 (and Access) ARE installed, the ACE Engine ODBC Drivers are NOT VISIBLE to the Host OS.
This is the reason for needing the ACE 2016 redistributable package released (as a .MSI install) .... so that scripting tasks or other 3rd-party apps can SEE and USE the ACE Drivers for CTR-installed Office clients!
Frank Rotolo commented
I think MS intentionally did this to force users to subscribe to an O365 plan that includes Access.