Re: Problems setting up access security

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Here is something that makes it even more confusing to me: I had her email
me the database, the workgroup file, and the shortcut, and everything worked
exactly as you would expect. I had to modify the shortcut to point to
different drive letter/path, but didn't change anything else. I can't access
the .mdb directly, others in my dept can't access the .mdb directly, and by
using the shortcut, we have to log in using the username/password that is in
the workgroup file. Basically, it works!

I'm confused. I'll look at the 2 things you suggested.

Thanks again! - Mike


"Joan Wild" wrote:

I'd only be guessing, but some possibilities:

The Admin user still owns the database object.
You secured it using the system.mdw, thinking that you were using your secure mdw.

--
Joan Wild
Microsoft Access MVP
"Michael D." <MichaelD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:C839E2BA-EA34-44C0-AD38-C57AA80113F0@xxxxxxxxxxxxxxxx
Joan,

I was able to successfully set up security on a couple of databases in my
area, and test them with multiple users on our LAN, including people from
remote geographic sites and the like, no problem.
But the person that I was trying to help (from another part of the
corporation) couldn't get your steps to work. So I went to her building and
went through the steps on a couple of different access databases, including a
little dummy one that I created on the spot. Everything seemed to work, but
for whatever reason, when ever someone other than her tries to open a secured
.mdb (ie, by going directly to the database itself), it lets them zip right
into the database. But when SHE tries to directly access the database, it
tells her she doesn't have permission (like it should for everyone).

The shortcut works fine, everyone can use it and log in using the
username/password combinations we set up in the workgroup file.

Any suggestions on the most likely thing I missed while at her desk that
would allow other users to access the .mdb file directly?

Thanks again! - Mike




"Joan Wild" wrote:

The location shouldn't matter. If you move it after the fact, you'll need to go into the properties of your shortcut and adjust the paths in the target to reflect the new location.

By the way, don't give your secure mdw the same name as your mdb. They each to create their own ldb file, and won't be able to if they have the same name.



--
Joan Wild
Microsoft Access MVP
"Michael D." <MichaelD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:9DFD0D8D-4AA3-46A8-A27C-8E1F08B6BE42@xxxxxxxxxxxxxxxx
Joan,
Thanks for the reply! I was just reading some stuff you'd written in
another post that seemed helpful as well.

I'm going to try your steps. I promise I'll go slow, despite feeling like
somewhat of an expert having gone through the steps so many times! haha..

One quick question: when securing a database, is it better to have the DB
on your hard drive and then move it and the workgroup file to the LAN, or
have the DB on the LAN and secure it from there? Or shouldn't it matter?

Thanks again! - Mike

"Joan Wild" wrote:

Setting up security is tricky, and if you miss even one step, it can result in an unsecure mdb.

I have the .mdw file on the network drive along with the database. Do I
have to go to every PC that will access this thing and merge the ...mdw into
their own local one?

No, you don't.

How does that prevent people from getting into it, as
anyone who I don't do this step for will still have access?

Exactly. If you set it up correctly, they should only be able to open the mdb while using the correct mdw.

I set a password
for Admin, moved Admin to the Users group, etc. But when someone else logs
in, they don't get a password dialog for Admin and they are in the Admins
group still...

Well, did you start by creating a new mdw?

Here's another step-by-step you could try. Don't skip anything!
www.jmwild.com/AccessSecurity.htm

--
Joan Wild
Microsoft Access MVP
"Michael D." <MichaelD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F0ED72F7-7313-45AF-B0E8-6ADD78D1C8F1@xxxxxxxxxxxxxxxx
I have an Access 2003 textbook, and 3 web tutorials, on how to set up
user-level security in Access. Although I feel like I'm doing it correctly,
when I put the database on the LAN, it only applies to me. Everyone else
just zips right into the database.

I followed the steps in the Access Security FAQ:

http://support.microsoft.com/default.aspx?scid=%2Fsupport%2Faccess%2Fcontent%2Fsecfaq.asp

The 10 steps here:
http://www.ltcomputerdesigns.com/The10Steps.htm

This article on about.com:
http://databases.about.com/od/tutorials/ss/usersecurity.htm

And the textbook Access 2003 Comprehensive Concepts and Techniques (Shelly
Cashman Pratt)

I have the .mdw file on the network drive along with the database. Do I
have to go to every PC that will access this thing and merge the ...mdw into
their own local one? How does that prevent people from getting into it, as
anyone who I don't do this step for will still have access? I set a password
for Admin, moved Admin to the Users group, etc. But when someone else logs
in, they don't get a password dialog for Admin and they are in the Admins
group still...

Confused! Frusterated! haha.. thanks for any guidance! - Mike







.

Relevant Pages

  • Re: Menu
    ... A database is not linked to a particular workgroup file. ... If my workgroup file has no password for Admin, ... because Admin should have no permissions to any ...
    (microsoft.public.access.security)
  • Help! Locked out of all databases after testing security...
    ... Selected the "Admin" user from the drop-down list and removed Admin from ... The strange thing is that the user name displayed is my Windows login name, ... I tried opening other database files by double-clicking on them, ... points to the location of the new workgroup file I created. ...
    (microsoft.public.access.security)
  • Re: Basic security questions
    ... So you have to provide the mdw in the connection string for this to work. ... > as well) to "open" the database ... ... ULS protected databases require the use of the .mdw workgroup file ...
    (microsoft.public.access.security)
  • Re: User access on a company intranet
    ... Access always uses a workgroup file, ... database, it silently logs you in as a user named 'Admin'. ... When you want to implement security, you create a new mdw file, and follow ... to open the secure mdb is by using the mdw you created. ...
    (microsoft.public.access.security)
  • Re: How to use an existing workgroup file with a new FE/DB databas
    ... joined to the standard workgroup file. ... Then, if people use the shortcut to open the database, it will open ok. ... > - add a password to admin and remove admin from the admin group ... specific instructions: adding & omitting nothing. ...
    (microsoft.public.access.security)