>>
>>That's because OLEDB doesn't load the ODBC manager .. even when going through and ODBC driver. The ODBC manager is the slowest part of ODBC.
>
>So, is the ODBC driver still involved to some degree, even when using OLEDB? I've had a few error messages with 'ODBC' in them, and was concerned that I was not actually using OLEDB like I am intending to. IOW, I need to *know* that I am actually using OLEDB. Here is how I am connecting...
>
>

>oConnection = CREATEOBJECT("ADODB.Connection")
>lcConnString = "DRIVER={SQL Server};" + ;
>	"SERVER=orange;" + ;
>    "DATABASE=testdb;UID=sa;PWD="
>oConnection.open(lcConnString)
>

>
>rutoh! Now you know the password!! :)

PMFJI,

That connection string is for ODBC, and what happens is that ADO uses the default OLEDB provider which is MSDASQL (for ODBC drivers). After opening the connection, check the oConnection.Provider property.

An OLEDB connection string for SQL Server looks something like this:
"Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Initial Catalog=testdb;Data Source=orange"