According to the Microsoft article this issue has been fixed.
One thing I ran into:
I have the 64-bit Microsoft Access Database driver installed but not Excel... switching to the ACE driver but running the 32-bit TestComplete/TestExecute "breaks"... you need to make sure that, if you're going to use that workaround, you have the proper "bitness" of the driver to match the bitness of the tool. Otherwise, it works nicely.
Thanks for the note, Robert!
Indeed, the bitness of the driver is important and must coincide with bitness of the TestComplete process. In fact, the "same bitness" rule applies not only to Excel, but also to all DB connections in TestComplete: starting from 12.40, you must pay close attention to bitness of data providers as 32-bit providers can only work with the 32-bit version of TestComplete and 64-bit providers can only work with the 64-bit version of TestComplete.
According to the Microsoft article this issue has been fixed.
