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

Linked tables & ODBC connection information

P: n/a
I'm using Access 2002 with linked tables to access an SQL Server
database. Authentication is done using Windows authentication (not
user id+password). As far as I can tell, when the table is linked,
connection information is copied into the access database (.mdb file)
itself, because when I put it out on the network for other users, they
do not seem to need a DSN to access the SQL Server database. Can I
count on the database having the connection information without the
user having the right DSN defined on their workstation?

Thanks in advance!

Aug 3 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Baz
The connection information is stored for each table, you can see it in the
MSysObjects system table.

<jo*********@gmail.comwrote in message
news:11*********************@l70g2000hse.googlegro ups.com...
I'm using Access 2002 with linked tables to access an SQL Server
database. Authentication is done using Windows authentication (not
user id+password). As far as I can tell, when the table is linked,
connection information is copied into the access database (.mdb file)
itself, because when I put it out on the network for other users, they
do not seem to need a DSN to access the SQL Server database. Can I
count on the database having the connection information without the
user having the right DSN defined on their workstation?

Thanks in advance!

Aug 3 '07 #2

P: n/a
You can go one step further and write a refresh script if your
connection information changes.

This works fine in my experience and if you need to force the password
into your connection, the backdoor method works fine.

I did what you might have done, and looked in the system tables for
the odbc fine and then wrote a refresh script to set a password.

In your case you must be using windws authentication?

Regards,
Tom Bizannes
Sydney, Australia

Aug 6 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.