New to Security

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello!

I would like to go through and set up security for an Admins group and Users
group on my databases. However, I am having a little trouble figuring out the
steps. I have the instructions from ms.com but is there anyplace clearer?

Also, what user ID's do I use? Do I use the user's LAN ID for the group?

Your help is much appreciated as I really need to secure the databases my
company uses.

Thank you,

Sandy S.
Database Coordinator
 
Hi Sandy,
I would like to go through and set up security for an Admins group
and Users group on my databases. However, I am having a little
trouble figuring out the steps. I have the instructions from ms.com
but is there anyplace clearer?
Click to expand...

Security is not simple, and you need to take the time to read up on it. I'd
suggest you practice on a copy of your database until you're comfortable.

You need to understand right off that you do not want to give the Users
Group (or the Admin user) any permissions. Not sure what you have from ms
website, but the definitive guide is the FAQ. Be sure to follow every step,
in order, or your database won't be secure.
Security FAQ
http://support.microsoft.com/?id=207793

The Security Whitepaper is also worth reading to help you understand.
http://support.microsoft.com/?id=148555

I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm
Also, what user ID's do I use? Do I use the user's LAN ID for the
group?
Click to expand...

You can use whatever usernames you wish. Note that Access security is not
integrated with windows security. Your users though may appreciate that
their username is the same for both, so they don't have two usernames to
remember.
 
Joan,

Thank you for the resources and the assistance. I plan to practice on my
hard drive as you've suggested :-)

I am curious however, I am supposed to set up the .mdw file but cannot
locate the WRKGADM.EXE to create it? Is it possible that because Access is on
a shared network that the WRKGADM.EXE is also stored on the shared server? If
so, do I just need to get permissions from our server administrator for this
file?

Or, is the WRKGADM.EXE an application integrated with Access and the .exe is
not accessible unless used through the security tools/wizard from the Access
..mdb file?

Sorry if I'm kind of ignorant on this subject. Your help is MUCH appreciated!

Sandy
 
Joan,

Sorry, one more quick question. Thanks again by the way..

If I have several database files that are linked to one main database (we
call them upfront modules - these are what the user accesses and the data
they write stores to one single database that they don't access). Can I
create one .mdw file for all of these databases to authenticate on?

Sandy
 
Sandy said:
Or, is the WRKGADM.EXE an application integrated with Access and the
.exe is not accessible unless used through the security tools/wizard
from the Access .mdb file?
Click to expand...

You didn't mention the version of Access, and it depends on that. In 97 and
2000 you use Start, Run, wrkgadm.exe. In 2002 and 2003 it is integrated
with Access (Tools, Security, Workgroup Administrator).
 
Sandy said:
If I have several database files that are linked to one main database
(we call them upfront modules - these are what the user accesses and
the data they write stores to one single database that they don't
access). Can I create one .mdw file for all of these databases to
authenticate on?
Click to expand...

Yes you can. Using the workgroup administrator, you can make your secure
mdw the default one to use, and secure all the databases with that one
workgroup.
 
Ok, great! I've got a practice security scenerio set up. My only minor
problem is that I do not want users to have the ability to "back-end" the
database if they hold down Shift when they Enter their name and password. If
that's not possible, is there any way I can lock them out of opening up
tables in recordset view to modify the data? (I want them only to edit data
using forms and or update queries).

Thanks again, you are Super!

Sandy
 
Sandy said:
Ok, great! I've got a practice security scenerio set up. My only minor
problem is that I do not want users to have the ability to "back-end"
the database if they hold down Shift when they Enter their name and
password. If that's not possible, is there any way I can lock them
out of opening up tables in recordset view to modify the data? (I
want them only to edit data using forms and or update queries).
Click to expand...

See
http://www.mvps.org/access/modules/mdl0011.htm
and
http://www.mvps.org/access/general/gen0040.htm
for disabling the shift key bypass securely.

You can deny all permissions on the tables and use RWOP (run with owner
permissions) queries - details in the FAQ.
In addition you can hide the location of the backend by putting it in
ahidden share on the server \\server\share$ rather than \\server\share.
They can only see it if they know the path
You can also add an autoexec macro to the backend that displays a message
(use the frontend) and closes the mdb.
 
Back
Top