Forum Discussion
Yeah... I think I'm with you on this that there is something environmental around the interface to Excel via the ACE driver... perhaps not necessarily a problem with TestComplete/TestExecute directly.
Have you tried moving the tests to a different machine with a fresh install of Excel? Also, the machine in question, is it running the 64-bit version of Office/Excel? Have you tried creating a "dummy" project to access a "dummy" excel file to see if the problem occurs there?
Just as a note, it is for reasons like this that I built my framework (and have been convinced to maintain the structure by guys like AlexKaras) around CSV files instead of Excel. There is just something about depending upon files created within a very particular piece of software as driving the data for a test project... I like Excel, I use it... but it is limited in it's portability and you are not the first person to complain about the reliability and stability of it as a data storage for long term use. Just my $0.02... and with conversion rates these days, that might not be worth a lot. ;)