security not requesting log in

[Guest]

I added security to my database. Some how one of the users is able to open
my database and add information and it is not requesting she log on. It
opens immediately to the main screen and shows her as Admin.

What do I do?

Thanks in advance.....Jen

 

[Rick B]

She is admin (in her own mdw file).

You did not secure your database. You skipped at least two very important
steps. If you had secured it, she would not be able to open it with her mdw
file and the Admin user would not have any access to the objects in the
database.

It sounds like all you did is go in and set up some users and groups with
permissions and stopped there.

You need to go back and follow *ALL* the steps involved in securing your
file. These need to be done in order. I would make a backup copy first.
The steps can be found in the following links:


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



Joan Wild:

www.jmwild.com/AccessSecurity.htm



Lynn Trapp

http://www.ltcomputerdesigns.com/Security.htm

 

[Guest]

Rick,

I have the Security.MDW file. I need to know do I copy the file onto a disk
and delete all the security files and create a new file. Basically do I
start over again?

Every other person that logs on it prompts for user name and log on. So I am
not sure why she is not being promted to log on with user/ password. I am
just worried about doing this all over again and crashing this database.

Thanks
Jen

 

[Rick B]

Again, stop taking shortcuts. You have skipped several important steps.
Yes, you could go delete her secure.mdw, but what if someone takes the file
home? Or what if you add a new computer?

Also, if a user deletes all the mdw files on their PC, then starts Access up
again, it will create a new mdw file.

You have skipped at least two MAJOR steps.

You should have removed all access to the objects in your database from the
"USERS" group. If you had done this, then no matter what mdw file she used,
she probably would not have been able to get to any of the objects.

Another step you should have performed is to secure the database file. If
you had done this, when she tried to start the file, it would have told her
that she did not have the needed mdw file. The same error would occur if
someone took the file home, or created a new "clean" mdw file, or if a new
PC is added.

You don't need to copy your mdw file to all the PCs. What if you want to
change someone's security? You plan to go to every PC? What if you fire
someone? Are you going to go ask them to move away from the PC so you can
lock them out of the file while they clean their desk?

The workgroup file should be on the LAN in the same folder as your backend
file.

You should NOT be replacing their workgroup file with yours. IF they create
their own file or try to open a template or a separate database, they should
not be logging into your workgroup file.


STOPPPPPP! Step back, and do this right. You are digging in deeper.

 

[Guest]

Okay, I think I got your point (kinda of like a first grader for forgetting
their homework) I will follow the instructions from the "jmwild" website
because it suited for 2003, my version. I will rate this after I attempted
to clean the mess I made up.
Thanks
Jen

 

[Guest]

Okay Rick I am in the home stretch,

I followed all the steps carefully. Now I noticed that it created a .bak
file. Do I want the individuals to use that file and not the mdb?

Thanks in advance

 

[Rick B]

No. I think that is just there in case you mess it up and need to get back
an unsecured version. I would save that and not let my users get to it.

 

[Guest]

Glad to have you in on the home stretch.

The mdb file is to be used.
--
***************************
If the message was helpful to you, click Yes next to Was this post helpful
to you?
If the post answers your question, click Yes next to Did this post answer
the question?