David91, I would do what JennyH11 and open a support case with SmartBear directly. It sounds like there is something incompatible with some recent MS Office updates. You can create a support ticket at https://support.smartbear.com/message/?prod=TestComplete
Unfortunately, the instruction I've been given is to disable Windows Updates to stop the issue from occurring.
I'm not sure this is a satisfactory response at present. Disabling Windows Updates is not something we want to do and would mean a change in process to how we currently work. I would usually expect the company releasing the software where the issue is displayed to act on the change made by Windows Updates... The software company I used to work would pro-actively test against the new Windows Updates when released and provide a patch if required to ensure their software functionality was unaffected and did not regress in any way for the customer.
I'm processing their response currently but that's my instinctive feeling on it so far....
I'm curious as to whether they've given you the same advice too David91
Thanks,
Jenny
The thing is that not every Windows update is necessarily available ahead of time to do testing against... so, while it would be nice to be able to make sure that TC works with every Windows update, that's not always any easy thing to do.
Question: For David91, his particular problem is that he has the 32-bit version of MS Office installed and cannot install the 64-bit driver to use the 64-bit version of TC 12.40. Are you in the same boat? Can you try with the 64-bit version of the Microsoft Access driver?
Additionally, try contacting SmartBear support directly... they may already have a patch or be working on one.
This is a know Microsoft Problem with the Jet Engine, that Microsoft say they are working on.
https://support.microsoft.com/en-gb/help/4041676/windows-10-update-kb4041676
BillSimpson wrote:
This is a know Microsoft Problem with the Jet Engine, that Microsoft say they are working on.
https://support.microsoft.com/en-gb/help/4041676/windows-10-update-kb4041676
That, and I believe that version 12.41 has TestComplete's fix for it as well. Contact support to be sure.
