User Level Security on Server

[Guest]

database developed using MS ACCESS 2003
Resides on server for multiple users. I need reference for establishing
user level security. If I use wizard on one PC, will it be in effect for all
PCs connected to server?

Thanks

 

[Rick Brandt]

database developed using MS ACCESS 2003
Resides on server for multiple users. I need reference for
establishing user level security. If I use wizard on one PC, will it
be in effect for all PCs connected to server?

When security is set up properly (and in the usual manner) then users will only
be able to open the file when they start an Access session with the correct
workgroup file and that workgroup file will require that they enter a UserName
and password before the file will open.

Most people setting up security for the first time botch it though and end up
with a file that everyone can still open or one that nobody can open.

Find some good step by step instructions and try it. Then go to another user's
PC and try to open your file without doing anything special. If you can open
the file then you didn't set up security properly (start over). If you cannot
then you did okay. Place your secure workgroup on the server and give each user
a shortcut that opens Access and your MDB using that workgroup file. The target
will look like...

"Path to MSAccess.exe" /wrkgrp "Path to MDW" "Path to MDB"

Using that, they should get a login prompt and should be allowed in if they
enter valid credentials.

 

[Arvin Meyer [MVP]]

database developed using MS ACCESS 2003
Resides on server for multiple users. I need reference for establishing
user level security. If I use wizard on one PC, will it be in effect for
all
PCs connected to server?

The data only should sit on the server. The database should be split, with a
copy of the application on each workstation, linked to the data on the
server.

User -level Security is usually best pointed to a workgroup security.mdw
stored on the server (for easier administration).

There are 2 schools of thought controlling whether and how the database on
the server is secured. If the users are not sophisticated, it is often
sufficient to leave the database on the server unsecured, save for the
security on the server itself. The file is placed in a secure folder that
only bonafide users can access.

If you need more stringent security, including possible exclusion of your
own users to specific data, deny rights to anyone other than the database
owner, and allow access only through WITHOWNERACCESSOPTION queries which
will be automatically built if you've checked the appropriate radio button
in Tools > Options > Tables/Queries > Query Permissions.

 

[Guest]

Thanks, I'll give it a try.

When security is set up properly (and in the usual manner) then users will only
be able to open the file when they start an Access session with the correct
workgroup file and that workgroup file will require that they enter a UserName
and password before the file will open.

Most people setting up security for the first time botch it though and end up
with a file that everyone can still open or one that nobody can open.

Find some good step by step instructions and try it. Then go to another user's
PC and try to open your file without doing anything special. If you can open
the file then you didn't set up security properly (start over). If you cannot
then you did okay. Place your secure workgroup on the server and give each user
a shortcut that opens Access and your MDB using that workgroup file. The target
will look like...

"Path to MSAccess.exe" /wrkgrp "Path to MDW" "Path to MDB"

Using that, they should get a login prompt and should be allowed in if they
enter valid credentials.

 

[Guest]

Thank you for your response. I think it is time for me to learn how to split
a database.

 

[Guest]

It appears that I have successfully split the database usint MS ACCESS
database spliter.

Now after I copy the BE to a folder on the server, I understand that I copy
the frontend to each user's PC. But how do I establish link between the FE
on the PC and the BE on the server?

Or I accomplish the split on the server and then copy FE to each PC?

Thanks

 

[Arvin Meyer [MVP]]

I always split the database and link a copy of the front-end on the server,
then I copy the front-end (already linked) to each user's workstation. I
keep a copy on the server to use in case someone corrupts their copy.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

 

[Ann]

I just started reading about security and even though it's overwhelming I
want to try it out. What is the advantage of putting a copy of the fe on
every workstation? Why wouldn't everyone use the fe on the server? Thanks
in advance.