I was apparently (*as is oft the case*) over thinking things and was under the impression that I had to be specific as to the type of ODBC driver being used. I changed the driver parameter from what was appearing as the driver type in the ODBC (the oraClient11g_home) with just "Microsoft ODBC for Oracle" (because it can't be that generic, can it?) and it worked perfectly. Again as a mea culpa, I thought you had to be specific about the driver. I'll also take your suggestion about using the DDT.ADOdriver. I was just trying to get the connection stuff working before I started in on acutally using it in a DDT. Thanks!