Is a DSN always necessary when using a SQL server back end?

[clancy76]

Hi all - I have an Access database that is using linked SQL tables via a DSN I created. I'm going to deploy the database to multiple machines soon - is there a way to do this without having to set up a DSN on every machine? The end users will only need read access to the SQL tables if that makes any difference at all. thanks!

[ranman256]

You can use code. It does the same thing as the DSN.

[pbaldy]

You can also use a File DSN stored on the server instead of a User or System DSN stored on your computer. I've done that but currently use what ranman suggested, which is often called DSNless code.

[clancy76]

Thanks guys! Will use the code, more and more people are asking for this db

[isladogs]

If, like myself, you use DSN-less connections and the basic (but old) SQL Server driver supplied with Access, you don't need to set anything up on each user's workstation.
All tables are linked using code.

If you need any of the latest features / datatypes in SS, you will need to use a newer SS driver and will need to ensure it on each workstation.