DSN-Less Connection to Oracle db

[Kirk P.]

I've read with interest all the posts on creating DSN-less connections. I
like the idea, and converted my Access db using a DSN-less connection to
retrieve data from an Oracle 9i database. The Access db file is located on
the network. When I run the pass-through query from my computer, everything
works perfectly. When I open the db and run the pass-through query from
someone else's computer (and supply my UID and PWD), I get the Access 3151
ODBC connection error message. I have verified that both computers have the
Oracle ODBC driver installed, and the references are identical. Here's the
connect string I'm using..

Set qdf = CurrentDb.QueryDefs("qsptCommissionable_Sales_ATL")

qdf.Connect = "ODBC;DRIVER={Oracle in OraHome90};
SERVER=PENPRD01;
DBQ=PENPRD01;
DBA=R;
APA=T;
EXC=F;
XSM=Default;
FEN=T;
QTO=F;
FRC=10;
FDL=10;
LOB=T;
RST=T;
BTD=F;
BAM=IfAllSuccessful;
NUM=NLS;
DPM=F;
MTS=T;
MDI=Me;
CSR=F;
FWC=F;
FBS=64000;
TLO=O;"

Now it could very well be that the fact I can't run the query from someone
else's compter using my UID and PWD is supposed to happen - maybe it's some
behind the scenes security thing - I don't know. But failing that, is there
anything else I should be doing to get this to work for all users across the
network? Our DBA's have kind of washed their hands of the problem because
the connection error is generated by Access, not Oracle.

Help me Obiwan, you are my only hope

 

[Douglas J. Steele]

Is there an entry for the DBQ member (PENPRD01) in the tnsnames.ora file?

 

[Kirk P.]

Your suggestion helped me "lead" our DBA to the solution. The other user had
an older version of the tnsnames file. When we updated his file, the query
works perfectly.

Thank you!