Following Joan Wild's Procedure but Not Working

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

Guest

Hi,

I have printed out Joan Wild's security procedure and have followed it to
the letter, but when I switch back to the system.mdw, I can open the database
with no problem.

I am using Access 2003. Basically, I did the following:
Opened Access (no database)
Noted the existing default mdw file
Created a new mdw and joined
Created a new user, entering name and PID
Added Admins Group to new user
Removed Admin user from Admins Group
Added a password for Admin user
Closed and re-opened Access
Logged in with new user
Set a password for new user
Ran the User Level Security Wizard
Kept default of securing all objects
Made sure Users group had no permissions (again, default)
Did not create any new users
Clicked next when got to step to either choose a group and assign users, etc.
Chose location for bak
Clicked finish and viewed/saved report
Closed db

If I then rejoin the default system mdw, I can easily locate the db in
Windows Explorer and simply open it.

Any ideas of what I'm doing wrong?
 
dee said:
If I then rejoin the default system mdw, I can easily locate the db in
Windows Explorer and simply open it.

Any ideas of what I'm doing wrong?
Click to expand...

Did you deny access to the *database* object for the Users group? It's easy
to miss, it's above "Tables" in the drop-down box.

Keith.
www.keithwilby.com
 
dee said:
I checked this, and they have no rights. (Nothing is checked)
Click to expand...

When you open a file using the default (or any non-secure) workgroup then it
is a given that you are doing so as the user 'Admin' member of the default
group 'Users'. A properly secured database grants zero permissions to both
of these entities and also makes sure that they are not the owner of any of
the objects.

If you can open your file as you have described then either Admin or Users
DOES have some permissions or else some ownership. There is no other
explanation.

Leaving Admin as the owner of the database is a very common mistake.
 
I have checked each and every permission and owner and they are all the new
user and *not* Admin.
 
dee said:
Hi,

I have printed out Joan Wild's security procedure and have followed it to
the letter, but when I switch back to the system.mdw, I can open the database
with no problem.

I am using Access 2003. Basically, I did the following:
Opened Access (no database)
Noted the existing default mdw file
Created a new mdw and joined
Created a new user, entering name and PID
Click to expand...

I would say right there is where you made your mistake. When you created a new mdw and joined it, that didn't change it for the *current session*. So you were still joined to system.mdw when you created a new user.

You should have quit Access, and restarted it to ensure that you were *using* the new mdw
 
Thanks Joan. I didn't see the instruction to quit Access until Step 11, but
you're saying I should do this right after Step 5?
 
While on this subject, I have one other question.

I will be housing my be on a network server and my fe (3) on individual
computers for data entry.

Will having the be on a password protected network driver/folder have any
impact on the fes? If for some reason we were to place the fe's on a network
server in another password protected folder, would this cause any problems?

Thanks for your help!
 
You need to be certain that you are using the correct mdw file when you create the new user. You can verify this by hitting Ctrl-G and typing
?DBEngine.SystemDB
That will tell you the one that is currently in use (not necessarily the one listed in the workgroup administrator as the default).
 
The secured folder for the BE shouldn't cause any problems - users need at least modify permission on the folder in order to use the BE.

Don't put the FE mdb files on the server - they should be on each person's PC. There are methods of updating the FEs when you make changes.
See http://www.granite.ab.ca/access/autofe.htm including some of the alternatives at the bottom of that page.
 
Back
Top