Thanx again for the response. Actually I am the Oracle DBA. I'm trying to
find a solution for one of our developers. We have VB code that works.
But, we've not been able to get a DSN-less pass-through query to work in
MS-Access using the "conventional" method of populating the Properties box
with a connect string. We either get an "ODBC call failed" or a pop-up
permitting us to choose a DSN. Well, we don't want to choose a DSN, we want
a dsn-less connection. I mean we're better off using "DSN=whatever" rather
than a connect_string. This way the user doesn't have to first pick a DSN,
then supply credentials; rather he/she only has to supply credentials. The
customer has agreed to this and I'm sure our Security unit prefers it this
way, since credentials aren't stored anywhere. Out of curiosity though,
I'll continue to play with this; never know when it might come in handy.
Thanx to all for your help.
"Dirk Goldgar" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> "Vince" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)
> > Thanx for the reponse.
> >
> > When I try your suggestion I get:
> >
> > "[Oracle}{ODBC][Ora]ORA-12560: TNS
rotocol adapter arror
> > (#12560)[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr
> > failed (#0)"
>
> We're getting closer! <g> I don't know what that means, though. Did
> the Oracle DBA give you that connection string? I have no experience
> connecting to Oracle. All I know is what I read at
>
> http://www.carlprothman.net/Default.aspx?tabid=81
>
> --
> Dirk Goldgar, MS Access MVP
> www.datagnostics.com
>
> (please reply to the newsgroup)
>
>