Access Security

[Guest]

Hi. Can anyone tell me whether there's another way to secure database other
than using "User-level security" ?

 

[Graham R Seach]

Firz,

You can use a database password:
Tools | Security | Set Database Password

You can encrypt the data:
Tools | Security | Encode/Decode Database

You (rather, your network administrator) can manage access/execute
permissions to the folder in which the database is stored.

Regards,
Graham R Seach
Microsoft Access MVP
Office DevCon 2007. Sydney Australia. Will you be there?
Sydney, Australia
http://www.block.net.au/devcon/index.htm

 

[Guest]

At this moment, I have 2 databases with the exact same designs. The only
difference are the permissions set to them. I believed that by using
"User-level security", the administrator can grant users access to different
tables, forms, queries and etc according to his wishes. So I was wondering
whether there is any other way to achieve this?

For e.g User A is allowed to access a particular table/form only by
read-only while User B is allowed to have the permission to have write
permission on it.

 

[Rick Brandt]

At this moment, I have 2 databases with the exact same designs. The
only difference are the permissions set to them. I believed that by
using "User-level security", the administrator can grant users access
to different tables, forms, queries and etc according to his wishes.
So I was wondering whether there is any other way to achieve this?

For e.g User A is allowed to access a particular table/form only by
read-only while User B is allowed to have the permission to have write
permission on it.

If you want to provide "guidance" to a group of well-intentioned users you can
create your own "security" system and how you implement that would be as
limitless as your imagination.

If you need "real" security meaning you need to enforce the rules against people
with possibly bad intentions then Access user level security is as tough as you
can get. Even that is easily broken if the person knows how to use Google and
is willing to spend a little money.

You can protect Access/Jet databases from non-users wtih network security. You
cannot provide robust security against people who are actual users of the file.
For that you need a server based engine like SQL Server.