Secured and Unsecured databases

[Guest]

Access security is new to me so I may have somewhat muffed up my first pass
at implementing it and need some guidance. I'm in the process of setting up
a multi-user database. When I set up user security for the database I want
secured, all seems fine. My concern is that now any time I go into Access it
requires that I log in. I should think that I should be able to apply the
security to specific MDBs. Did make a mistake or is this normal? I used the
security Wizard to initially set up security. Thanks for any help provided.
Let me know if additional information is needed.

 

[Joan Wild]

Access security is new to me so I may have somewhat muffed up my first
pass
at implementing it and need some guidance. I'm in the process of setting
up
a multi-user database. When I set up user security for the database I
want
secured, all seems fine. My concern is that now any time I go into Access
it
requires that I log in. I should think that I should be able to apply the
security to specific MDBs. Did make a mistake or is this normal? I used
the
security Wizard to initially set up security. Thanks for any help
provided.
Let me know if additional information is needed.

Access ships with system.mdw and security is already implemented whenever
you use Access. For all databases, it uses this system.mdw file and
silently logs you in as the 'Admin' user which has full privileges.

When you implemented security and created a new mdw file, Access made it the
default one to use. This is why you are getting the login for all
databases.

You don't mention the version, but the wizard likely made a desktop shortcut
for you to open your secure mdb.

You can use Tools, Security, Workgroup Administrator to rejoin the standard
system.mdw as your default. Use the desktop shortcut for your secured mdb.
Actually a good test to see if you implemented security properly is to try
and open it without using the shortcut.

 

[TC]

It sounds like you are not using a list of written instructions. It is
very difficult to get it right, unless you follow an explicit list of
written instructions - adding & omitting nothing. Maybe try the Access
Security FAQ, often referenced in this newsgroiup.

HTH,
TC

 

[Guest]

Access ships with system.mdw and security is already implemented whenever
you use Access. For all databases, it uses this system.mdw file and
silently logs you in as the 'Admin' user which has full privileges.

When you implemented security and created a new mdw file, Access made it the
default one to use. This is why you are getting the login for all
databases.

You don't mention the version, but the wizard likely made a desktop shortcut
for you to open your secure mdb.

You can use Tools, Security, Workgroup Administrator to rejoin the standard
system.mdw as your default. Use the desktop shortcut for your secured mdb.
Actually a good test to see if you implemented security properly is to try
and open it without using the shortcut.

Joan, thanks. Your recommendation worked. Somehow I missed the link that
should have been created on my desktop. It might have been created and then
I deleted it thinking I had made it by accident. As for the Access version,
we're on 2002. I know I joined the new MDW instead of attaching it to the
link which I will do now.

 

[Guest]

Actually I followed the help in Access. I wasn't aware of the FAQ at that
time but have since become aware of it from my readings here. Thanks.

gt

 

[Guest]

Take it from somebody who knows, the wizards are a great help, but you often
need more help than just that. I found this out the hard way myself. I can't
recall how to find any of them, so please help me out if anybody can recall,
but there are plenty of places online to find a step by step guide to make
sure you implement everything right. They can be long, but it is better to
take a little more time to get it right.

--
Have a nice day!

~Paul
Express Scripts,
Charting the future of pharmacy

 

[Guest]

What really annoyed me about this situation is that I'm an infosec
professional by trade. I've done security in all kinds of systems and
applications. I decided to build a little database for our department's
monthly status reports to replace our current arcane, manual method.
Employing Access security has turned out to be interesting to say the least.
I wish I could have built the backend in MS SQL but that would have required
an official project and all the headaches that would have entailed.