Access to SQL server from Microsoft Access application

A file DSN does not prohibit the use of the credentials of the user.

But first of all: What do you mean with "their own credentials"? Windows Authentication or SQL Server Authentication?

Then, using one shared Access front-end is a bad practice, cause it may lead to increased corrupted front-end database files. Each user should have its own, local copy of the front-end.

And last but not least: Use DSN-less connections. See

https://www.experts-exchange.com/questions/27835736/How-to-create-an-Access-database-with-a-DSN-less-linked-table-to-a-SQL-database.html

I prefer to use DSN-less connections.

No points please.

Sorry, "Users own credentials" yes that is Windows authentication.
I will try this DSN-less connection, but it's 100% clear for me where to enter this?
Can you clarify?
Thanks

<<Sorry, "Users own credentials" yes that is Windows authentication.>>

 That's a setting in SQL Server.   You have two choices for security with SQL: SQL Logins or Trusted Connections.

 You want the latter, which means SQL will assume that since they are logged into Windows, it should trust the connection.

 This is different than a DSN or DSN-Less, of which you can use either.

With a DSN-Less connection, all that says is that you've supplied all the information in the connection string and don't need a DSN to complete the connection.

 If you are using SQL Logins, then that means a username and password must be setup in SQL Server and supplied as part of the connection string (either via a DSN or without) in order to get a connection.

Jim.