You need to make sure, then, that in your connection string, you're referencing the 64-bit ODBC driver... I'm assuming it has a slightly different name. Do that, and you can use the 64-bit TestComplete
Got you, its about the system ODBC Data Source Administrator.
Yes, I have added the Microsoft Excel Driver under both User DSN / System DSN - in both 32bit ODBC and 64bit ODBC.
We are able to work along with 32bit TC, just trying to resolve this outstanding issue as we got some free time :) Thanks for your help tristaanogre
You need to make sure, then, that in your connection string, you're referencing the 64-bit ODBC driver... I'm assuming it has a slightly different name. Do that, and you can use the 64-bit TestComplete
You are absolutely right. Have not noticed that till now, just updated the connection string
from
"DRIVER={Microsoft Excel Driver (*.xls)};"
to
"DRIVER={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};" and it worked.
I have no idea how the previous one worked all these days when the actual name in the ODBC is
"Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)"
Even now the old previous connection string works for TC 32bit.
Anyway thanks a lot tristaanogre
Good to know that it's fixed!
One thing you might want to consider doing is a detection of whether or not you're running the 32-bit or 64-bit TC and, depending on that answer, set the connection string appropriately.
tristaanogre, "DRIVER={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};" works for both 32/64 bit TC. That's what we have in both 32/64 ODBC.
Its just some miracle that "DRIVER={Microsoft Excel Driver (*.xls)};" works for 32-bit.
