Previously, users were required to install the Access Database Engine (ACE) Redistributable (or “redist”) to expose ACE outside of the Office bubble. Upon transferring data between existing Microsoft...
Updated Feb 11, 2020
Version 2.0
Blog Post
Hi denniwil,
Thanks for your reply.
However it has nothing to do with older MSI- nor older C2R-versions of Office being preinstalled. It has been confirmed on clean Windows OS with Office C2R-versions only installed (Office 2016, Office 2019, Office 365 and Microsoft Apps 365). The versions 2010 release starting from 10th November 2020 and also the following and record-replacing version 2011.
What I notice in the code is that what worked in older Office-versions dating even back to Office 2010 (MSI) with ACE2010, Access 2013 Runtime and ACE2016, stopped working. When the AceCore warning appears, I see that a previously ODBC handle value that was closed using SQLDisconnect is being returned in the afterfollowing SQLDriverConnect which was called with different connection string (another MS Access db-file).
I have not been able to reproduce it in a demo solution to send it in to Microsoft Premier, but this occurs when MFC application A starts MFC Application B and both are accessing several MS Access files using ODBC functionality residing in a MFC DLL.
Best regards,
Kim