Security without passwords

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

Guest

I've set up a database in Access 2002. I'd like to protect the database, but
almost in a reverse method to the conventional. I'd like all users to be able
to access the database without a database, but if a user wants to make
changes or delete certain data (for example) then they would be required to
use a password.
The reason we want to do this is that there are already so many different
programmes that require passwords that users become reluctant to use them.

From what I've read it seems the standard route is to set up user groups and
then assign individuals with passwords but this is not what we want.
Suggestions welcome as usual!
 
Thanks Joan,
I've gone through your step by step security set-up.
As I want users access the database without a login, and am using Access
2002, I enter 'No' at step 24.
At step 25 I have me (Graeme) as one user and there is a prompt "Add new
user". Do I add a new user or click next at this stage? (At step 25 your last
line reads "It is recommended that you select this user and enter a
password... - who is 'this' user? A newly created user I presume)
I presume there should be a second security group - if so can I set up
optional groups so that this (user) group are 'new data users'?
Do I still create passwords for other users even though there is no login?
 
--
Joan Wild
Microsoft Access MVP
Thanks Joan,
I've gone through your step by step security set-up.
As I want users access the database without a login, and am using
Access 2002, I enter 'No' at step 24.
Click to expand...

Well you should choose Yes. You do want to assign permissions to the Users
Group. That way, they'll be able to use their standard system.mdw and no
login will be required.

You just don't want to assign permissions to any of the other groups the
wizard offers, nor do you want to create any new groups.
At step 25 I have me (Graeme) as one user and there is a prompt "Add
new user". Do I add a new user or click next at this stage? (At step
25 your last line reads "It is recommended that you select this user
and enter a password... - who is 'this' user? A newly created user I
presume)
Click to expand...

You don't need to create any users, since you want your users to just be
silently logged in as 'Admin' using their system.mdw workgroup file. The
password is the password for the Graeme user, yes.
I presume there should be a second security group - if so can I set up
optional groups so that this (user) group are 'new data users'?
Do I still create passwords for other users even though there is no
login?
Click to expand...

No need to setup any additional groups or users.

You'll have a secure mdw with Graeme user in it, and this user will be a
member of the Admins Group and own everything. When you want to make
changes you'll use the secure mdw and login as Graeme.

Since you've assigned permissions to the Users Group, all you need to
distribute is the mdb file. Users will use their default system.mdw
workgroup. The Users Group is common to all mdw files (but the Admins Group
is not). So your users will get the permissions that you assigned to the
Users Group.
 
Ok,
got that.
When I 'finish' (step 29) I don't get any report.
It seems that Access is trying to process, it says 'securing objects' at the
bottom of the screen but then nothing happens. Thought I'd leave it for a few
minutes but it appears to get stuck.
Now I'm stuck!
Cheers,
graeme
 
You can always secure it manually. There's nothing the wizard does, that
you can't do yourself. The instructions are on the 97/2000 page.
 
Ok,
looks like I got the wizard to secure (rather than manually).
When clicking the wizard generated shortcut I am asked for a password to
login as 'Graeme'. I did not create the desktop shortcut with the target
"path to msaccess.exe" (as I do not understand that! Is it supposed to be c:
.....system.mdw ?)
Lastly, the following seems incongruous with the 2nd last paragraph on the
link (..Do not create new groups or assign permissions to the group offered
by the wizard.)Thanks Joan,
 
The wizard generated shortcut is fine. If you want to right-click it and
choose properties, you'll see the target line and what's in it (just fyi).

You are following the step-by-step which is for a typically secured mdb
(where no permissions are given to the Users Group). But you do want to
give permissions to the Users Group, in order to distribute the mdb and not
require them to log in.

In your case, you want to assign permissions only to the Users Group, and
not create any other groups, or use any others. You will be a member of the
Admins group and have all control, while your users will just use their
default system.mdw workgroup file (and be silently logged in as 'Admin' user
which is a member of the Users Group).
 
Joan,
thanks for bearing with me.
I've followed the step by step from step 16.
As far as I can tell the permissions I set are for read only (step 24). So
how do normal users access the file? Assuming that the file sits on a network
drive and that users each have a desktop shortcut.

Below find my Users (I've changed the passwords)

Name: Graeme Leach
Personal ID: apPvY5XHFetc
Password: fishie
Groups:
Admins
Name: admin
Personal ID: <Previously Created>
Password: LAIZiwhetc
Groups:
Users
 
Your users simply open the mdb file. They'll be doing so using their default
system.mdw workgroup.

They'll be 'silently' logged in as 'admin' and therefore have the
permissions you gave the Users Group.

You can verify the permissions the Users Group has by opening the mdb using
your secure mdw and going to Tools, Security, Permissions - choose Groups
and select the Users Group.

That group should have Open permission on the database object, and at least
read data permissions on the tables/queries, and Open permission on the
forms and reports.

When you want to make changes, you'll use your secure mdw workgroup and
login as Graeme Leach and make changes. Then just provide the updated mdb
file to the users.
 
Thanks,
it works.
I had not set Open permission on the database for Users Group!!!
Cheers,
Graeme
 
Back
Top