Question User Level Security

[moori]

User Level Security: Table access

Hello everyone,

I have a question about user level security / access control.
For my database I have a back-end containing the tables and a front-end with forms, queries and everything. I have set up the access user level security.

Dependent from the access level of my users, some front-end options will be hidden and some queries retrieve only part of the data. For example: I have a form to calculate clients' end prices. A vendor can only see prices for his own clients, not for other vendor's clients.

BUT: to make the query work, all users need access to the tables and the back-end must be stored in a public place, right? Now all vendors can just open the back-end and see all information.

What can I do about this? Maybe protect the BE with a password and store this in the queries? Any hints are appreciated!

 

[boblarson]

Access isn't all that secure. If you need better security, you'll have to move to using SQL Server, SQL Server Express, or some other more secure database for the backend.

You can set a password on the backend (although it can easily be hacked if you know what you're doing) and then you will have to relink the tables and you may have to check the Save Password checkbox when you are doing the linking from Get External Data > Link Tables.

 

[moori]

Yes, this was what I was looking for! I didn't think it would be so easy, I thought I would have to add the password to every query and VBA module or something like this.

Thanks for the security hint, but these measures are sufficient at the moment. The Database itself is stored on a SQL server, so it is protected against the "outside world".

Gracias!

 

[moori]

PS: how do I mark the thread as "solved"?

 

[boblarson]

I was talking about ACCESS LINKED TABLES, not SQL server tables and I'm not sure what you mean by the Database itself is stored on a SQL Server. If the tables are in a SQL Server database, that is different.

For SQL server tables you would need to create SQL users in the security and then you would grant them roles or set the permissions on certain items to be readable or executable by only those individuals. But if you have your SQL Server

 

[moori]

No, it is an access database.
What I meant is just that the company has a professional server (which I assume to be SQL, but if I am talking nonsense: don't mind me, I am just an amateur). The database I created is just for my department and stored on what everyone calls "the server"

 

[boblarson]

There is a difference between SQL Server and Windows Server. You are talking about a Windows Server.

 

[moori]

Oh, ok... yes, that makes sense :-D