By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,474 Members | 1,273 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,474 IT Pros & Developers. It's quick & easy.

DSN Behaving Badly

P: n/a
I have created a file DSN on my PC, and am using it to provide one of
the two connections required for an Access query.

(The other connection uses the PostGRE SQL connection and works as
expected.)

When I created the DSN, I specified that it should use SQL Server
Login as the authentication method, prompting the user for
credentials.

This all works and I get a successful test in the ODBC Microsoft SQL
Server Setup window.

However, when I attempt to run the query, I get a "Connection Failed"
error and I can see that the connection is attempting to log into the
database using my trusted (LAN) login.

I can then tell it to stop trying to to log into the database using
trusted login and do what I said in the first place. If it was just
me, I'd probably keep doing that, annoying as it is.

Problem is, users with the runtime version of Access never have the
option to tell the DSN to behave.

Anyone know what's going wrong with my DSN?

I have rebuilt the connection and the query and the DB twice, but to
no avail.

How do I force the connection to behave the way it was instructed to
when I built it?

Thanks,

Patrick
Feb 26 '08 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.