Question : Ms Access to SQL Server DSN or connection string

Hi Experts--  Lots of info on this subject but I can't seem to find an example that pertains to my situation.  I have an Access 2003 application that uses a SQL Server 2005 DB backend.  The Access application and SQL Server reside on the same server and access uses linked tables and a system DSN to connect to the Database.  This setup works just fine if you open the application ON the server where it resides, but we have several users who connect to it via a shortcut to the .mdb (across the network).  

Is there a way that I can have everyone access the application/db w/o setting up a similar system dsn on each of their machines?  I've been trying to explore connection strings and such but I'm not sure exactly what to put where...  Would I place the connection string in the onload event of the first form to open? Does it matter that the access app physically resides on the same server as SQL?   Do I reference the existing system DSN?   What exactly would the connection string/dsn-less code look like?

Any help appreciated... Thanks.

Answer : Ms Access to SQL Server DSN or connection string

When the app is opened using the shortcut, does it run on the server (would have to be Citrix, terminal server or RDS) or does it then use a copy of access on their PC? If the latter, then you need a dsn on that PC - or dsn less connection

The other issue will be SQL authentication & you'll need to check out the security settings in SQL for that database


Kelvin