[AccessD] Linked to SQL Server in a domain

The DSN does not have to be on each client system.
It could reside on a common UNC path that everyone has read/write permissions.
I had a similar situation where a Access database FE tapped into a SQL Server data repository.
By having the DSN on a common mapped drive everyone could copy the FE to their machine and still use it with SQL Server without problems.
 
Jim

________________________________

From: accessd-bounces at databaseadvisors.com on behalf of Susan Harkins
Sent: Thu 5/21/2009 18:03
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Linked to SQL Server in a domain



> I am assuming that is because the DSN file I used to do the link is not on
> her computer?  Is that
> the way this works?  How do I discover where the DSN file is for the
> database that existed already
> when I first got in?  I tried looking at the TDF cnn data and it isn't
> referenced in there.

Yes, the DSN  must be on each client system. Via Control Panel,
Administrative Tools, Data Sources (ODBC) you'll find existing DSN's listed
in the System DSN and File DSN tabs.

Susan H.

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com <http://www.databaseadvisors.com/> 



################################################################################
If you have received this message in error, please contact the sender
immediately and be aware that the use, copying, or dissemination of 
this information is prohibited. This email transmission contains 
information from NCI Information Systems, Inc. that may be considered 
privileged or confidential and is intended solely for the named 
recipient.
################################################################################