Philipp Stiefel
According our contact at Microsoft Premier, it was already officially released from version 2010 released 10th November last year (2020).
You can try out yourself by downloading the officially released Click-to-run Office versions as I stated in my previous post using SqlDriverConnect (ODBC) or OleDispatchDriver (OLE).
Version 2012 has been been released since I wrote last time and the warning message still prevails. In one use case it also actually crashes in
What leads me to think it's a bug is:
* Works with ACE2010, Access 2013 Runtime and ACE2016
* If the Access DB file is opened first with SqlDriverConnect and then opened with OleDispatchDriver, it doesn't display any AceCore warning. Switch the opening order then the message shows up. The warning also shows up in some combination of calls SqlDriverConnect and CDatabase::OpenEx.
Updated 2021-01-26:
It is confirmed by Microsoft as being a bug in Office with built-in ACE and planned to be fixed in May/June.
Support case [Case #:23694309] - https://serviceshub.microsoft.com/support/case/121011425003844
We are discussing internally if it is required with a hotfix prior to the plan.
Kim