🚀 go-pugleaf

i don't think this is completely correct, but i am mixing environments in my
defense... from what i learned, the ODBC sits on top of a SQL*Net layer...
w/out that layer, ODBC can't make the connection...
with ADO, we didn't have to use the ODBC driver, but we still needed the
lower layer (but in this case, we were using MSSql and it's stuff - not it's
ODBC, tho)... maybe we were doing something wrong, but it always required
the sql dll (forget the name, but it's what showed up when setting up the
client in MSSql)....

i may be wrong, but we never got this to work w/out the native connectivity
s/w, sqlnet or whatever....

good luck!
brent

Charlie Barrett wrote in message
<76Vu3.13894$vu2.3852@news.rdc1.tx.home.com>...
>Yep, your remote machine needs to have either the Microsoft OLDDB or ODBC
>driver for Oracle, which I think is a standard driver included in Windows,
>but probably needs to be updated (see http://www.microsoft.com/data/ ). You
>then need to get into the Control Panel, select ODBC, and assign a
>connection string to your Oracle server.
>
>Then you can use ADO, DAO, or whatever to connect to the Oracle server
>through the connection string you assigned in the ODBC driver.