Re: Database, its security and a server.
- From: "Keith Wilby" <here@xxxxxxxxx>
- Date: Wed, 3 Jan 2007 14:43:57 -0000
"Douglas J. Steele" <NOSPAM_djsteele@xxxxxxxxxxxxxxxxx> wrote in message
news:%23$on9I0LHHA.5000@xxxxxxxxxxxxxxxxxxxxxxx
If they're able to get into it without getting a log-in prompt, then you
didn't apply security correctly.
Make sure you've read
http://support.microsoft.com/default.aspx?scid=%2Fsupport%2Faccess%2Fcontent%2Fsecfaq.asp
thoroughly several times.
Look in section 1 (What are the steps to help protect a database?). I'm
guessing you missed step 6 (Remove the Admin user from the Admins group so
that Admin is a member only of the Users group.) Because you didn't do
that, and the users are using a different MDW file than you used to secure
the database, they're all getting in as Admin (the default user id)
Just to add to Doug's response, you should join your workgroup on a
session-by-session basis using a shortcut with a command line formatted as:
"Full path to MSACCESS.EXE" "Full path to your database.mdb" /wrkgrp "Full
path to your WIF.mdw"
including quotation marks. That way users won't be prompted to log on to
"unsecured" database files.
Regards,
Keith.
www.keithwilby.com
.
- References:
- Re: Database, its security and a server.
- From: Douglas J. Steele
- Re: Database, its security and a server.
- Prev by Date: Re: Database, its security and a server.
- Next by Date: Re: Can I Set permissions for a .mdb using Windows login?
- Previous by thread: Re: Database, its security and a server.
- Next by thread: Re: Can I Set permissions for a .mdb using Windows login?
- Index(es):
Relevant Pages
|