That VbScript worked in XP, Why Not Now?

Posted on January 30, 2014 by Alan

Do you have a script that worked with your x32 XP computer, but no longer works in Windows 7 or 8 x64? I am finding that some of the scripts I wrote have this problem. Somethings may rely on an ActiveX control that was native to XP but not a later version. What I am finding is that I have some scripts, such as this fragment fail:

Set OConnMDB = CreateObject("ADOX.Catalog")
 	OConnMDB.Create _
 	    "Provider = Microsoft.Jet.OLEDB.4.0; " & _
 	        "Data Source = " &dbName 
 	Set OConnMDB = Nothing

A quick fix for this is to run the script with the X32 version of cscript or wscript. You can try running the scripts with c:\windows\SysWow64\cscript.exe. Otherwise, back to the debugger.

You must be logged in to post a comment.

All the scripts are saved as .txt files. Newer files have a “View Script” button which will let you save or open a script in notepad. For earlier posts, the easiest way to download with IE is to right click on the link and use “Save Target As”. Rename file from Name_ext.txt to Name.ext.

To see a full post after searching, please click on the title.

PowerShell Scripts were written with version 3 or later.

https connections are supported.

All new users accounts must be approved, as are comments. Please be patient. If you find a post error or a script which doesn’t work as expected, I appreciate being notified. My email is my first name at the domain name, and you are welcome to contact me that way.

Leave a Reply