Need help making a connection

I'm an old VB6er moving into the world of cscript and vbscript. I've copied and pasted code from websites that say this is how to open a recordset, etc., but my issue is that I get an error 424 (Object Required) right up front on the line that creates the connection and everything tanks from that point onward.

Set SQLcon = CreateObject("ADODB.Connection")
if err.number <> 0 then
 sline = "Error " & err.number & " creating connection" & vbcrlf & err.Description
 wscript.echo sline
 logfile.write (sline)
end if
set rs=Createobject ("ADODB.Recordset")
if err.number <> 0 then
 sline = "Error " & err.number & " creating recordset" & vbcrlf & err.Description
 wscript.echo sline
 logfile.write (sline)
end if
SQLcon.Open "dsn=Flatcurrent"
rs.CursorLocation = adUseClient
rs.open "select top 1 * from tblProgress",adopenstatic,adlockoptimitic
if err.number <> 0 then
 sline = "Error " & err.number & " opening recordset" & vbcrlf & err.Description
 wscript.echo sline
 logfile.write (sline)
end if

All variables are declared at the beginning of the module.  What's causing this?  Is it unable to resolve ADODB.Connection? 
 
MDAC version is 2.8, running on WinServer 2003, SP2.

So you are running this as a stand alone VBScript?

Yes, under cscript.

you can check Classes Root in the registry for a definition of ADODB.Connection. Other than that I can't think of a reason why it wouldn't be able to instantiate the object.

ebgreen


you can check Classes Root in the registry for a definition of ADODB.Connection. Other than that I can't think of a reason why it wouldn't be able to instantiate the object.

It's there.  Shows CurVer = ADODB.Connection.2.8

I've only got one instance of cscript.exe, in C:\Windows\System32.
 

I just checked because I remember having a problem recently using ADODB on my machine and launching the script using Windows\SysWOW64\cscript.exe was what I needed.  Maybe try reinstalling MDAC?

dm_4ever


If running on 64bit...you might try and navigate to the 32 bit version of cscript and launch your script using that.

Okay, you got me thinking.  SysWOW64 isn't on this machine, so I copied a 32 bit version of cscript from another machine and ran using it.  That was the solution - no more errors.
Thanks!