so although test complete claims to be a 64 bit application, when I added the driver for 32 bit testcomplete after removing the 64 bit driver, it works as it has been.
What version of TC 12 are you running? What "bitness" of Excel is installed?
Note that there are some requirements wrapped around bitness for using Excel versions. See https://support.smartbear.com/testcomplete/docs/testing-with/data-driven/excel-storages.html#requirements I'm assuming that, when you upgraded to 365, something changed in those areas. See if any of this helps.
Thanks Robert. I have office 365 version of excel and test compete 12.10.590.7
Curiously, I can use the ddt driver with another project from my laptop and it works fine. This leads me to suspect there is some setting on the project that is screwing up the ddt driver but have not been able to find it.
so I tried creating both a new project as well as a new project suite, this did NOT work for my spreadsheet but did for my co-worker's spreadsheet. I noticed that his spreadsheet is using the extension .xls where mine is stored as .xlsx unfortunately, I am still getting the error after I copied my spreadsheet to xls format....
Again... verify the bitness. Are you using the 64-bit Office 365 or the 32-bit?
IIRC, in order to use the Excel DDT, you need to have a 32-bit Excel ACE driver installed, even if you're using 64-bit TestComplete.
64 bit Office / Excel and 64 bit test complete . Am double checking the link now......
