Hi,
I understand the situation this way:
-- When you execute standalone VBScript, you are running it from the 64-bit command prompt using 64-bit VBScript engine that looks in the 64-bit registry for the requested provider;
-- TestComplete is 32-bit application, thus it uses 32-bit VBScript engine and is looking in the 32-bit registry for the provider. As the provider was installed as 64-bit application, it is not present in the 32-bit registry and thus script fails.
I don't have exact solution at hand, but would suggest to search MS site for the 32-bit version of the ADO provider that can work with your Excel file.
Also you may consider to look into 32-bit Office installation and try to install only ADO from there.
