thanks for your reply.
I'm not aware of another way to get all sheets of an Excel File.
The sheetnames I get here, will be used later to load the sheet data with normal biff load (ooxml).
For example if a sheet does not exist in an Excel file, QV would give you an error. Another usecase would be to work around mistakes in Sheetnames.
What connection string are you using? I have used the following without too many problems:
ODBC CONNECT32 TO [Excel Files;DBQ=$(vReportDefinitions)];
Where vReportDefinitions is a relative path to the xls file. If you on a 64 bit machine, this script will attempt to use the 32 bit driver. If you want it to use a 64 bit driver on a 64 bit machine, the just use CONNECT rather than CONNECT32. This form will use 64 bit driver on a 64 bit machine and the 32 bit driver on a 32 bit machine.
I dont know if this is helpful for you...
I do it the same way. (pls attached example file)
Connection works only with "ODBC CONNECT32" or "ODBC CONNECT64". Which is not (yet) a big problem.
Here I have to use CONNECT32. I'm not 100% sure but I think it depends on the QV/office version used not on the machine(windows) version?
As I wrote earlier ... "in general everything works ok" ... (people seem not to read this or I express myself not clearly)
Call me complicated or too much detail oriented, but I like things to work as smooth as possible. So if there are questions from target group, I want those questions to be content related not nerdy technical issues.
For example: Try to explain the issue about 32/64 bit to end users, it stops exactly at the point when you say something about "32/64bit" ---> ??? ..
Anyway the most annoying thing is the error interrups script execution even when ErrorMode = 0. Which is the opposite behavior to what is written in the qv manual?
example.qvs 920 bytes