With the Teradata ODBC driver, you employ the "Kagera' MSDASQL Generic OLE DB Provider from Microsoft (comes standard with MDAC) to perform the translation from ADO to ODBC.
I use a DSNless connection
set up a connection string
mobjADOConnection.ConnectionString="PROVIDER=MSDASQL;" & _
"DRIVER={Teradata};" & _
"DBCName=" & mcstrGDWservername & ";" & _
"DefaultDatabase=" & mcstrGDWDatabasename & ";" & _
"UID=" & mcstrGDWLoginID & ";" & _
"PWD=" & mcstrGDWPassword & ";"
eg.
mobjADOConnection.ConnectionString="PROVIDER=MSDASQL;" & _
"DRIVER={Teradata};" & _
"DBCName=dbccop1;" & _
"DefaultDatabase=ProdDB;" & _
"UID=myuserid;" & _
"PWD=mypassword;"
then continue with normal ADO commands (Open the Connection, Execute a Command or Open a Recordset with an SQL string, then process the recordset)
Make sure you have MDAC (Microsoft Data Access Objects) (MDAC2.7 is latest version, but earlier versions from MDAC2.1 work fine) - it is a free download from Microsoft.
I suggest you use a name for DBCName rather than an IP address (via Hosts file etc) to enable the actual address to be changed without
re-coding impact
Regards