VBScript, HTAs, ODBC and 64-Bit Windows

[Michael42]

Hello,

1. Is VBScript on Windows 2008 RS 64-bit run as 64-bit applications?

2. What ODBC Data source Admin version should I use for a VBScript (the 32 or 64 bit)?

I have drivers installed for both for Oracle. Thus far all my VB6 apps (using the 32bit ODBC) are working fine but not some new scripts I am trying to write in VBScript.

EDIT: I am trying to use VBScript as an HTA app.

Thanks,

Michael42

 

[markdmac]

VBScript is 32bit.

Feel free to post your code along with any errors you are getting for help in troubleshooting them.

If you have to use 32-bit ODBC drivers, you won’t find them when you start the Microsoft ODBC Administrator because it is 64-bit. The 32-bit ODBC Administrator is found here: C:\Windows\SysWOW64\odbcad32.exe

I hope that helps.

Regards,

Mark

No trees were harmed in posting this message, however a significant number of electrons were terribly inconvenienced.

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER.

 

[xwb]

It it doesn't work, try running it from the 32-bit cmd prompt in C:\Windows\SysWOW64\cmd.exe

Basically everything is the wrong way round on a 64-bit machine

C:\Windows\System32 is 64 bit
C:\Windows\SysWOW64 is 32 bit

 

[Michael42]

Thanks for the posts. That makes this much clearer.

Wish VBscript had a different way to get to Oracle data besides ODBC. When it was JUST 32-bit it was interesting enough. An Oracle OCI driver that worked with VBscript would crazy great.

Yep I am familiar with Oracle's ODP\.Net\VB client stuff. Yikes!

Just say'n, OCI based connection code or even JDBC is much easier to work with at this point.

Thanks,

Michael42

 

[markdmac]

XWB, not to hijack the thread with a sidebar, but I agree with you. Dumbest move Microsoft made when they went to X64 was not making a Program Files (x64) folder. They tried to keep the naming convention the same for all new apps and screwed over all the old ones.