Wizard not working - Database not secured

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

Guest

I have used wizard several times now and it does not secure my database. I am
able to open my database by just double clicking on it while I am connected
to the default system.mdw. I have followed Joan Wild's "Access 2002/2003
security Step by Step" and used both methods: by creating the username that
matches the windows username and by creating a new one as well. The wizard
does create a shortcut which on opening prompts for a username and password.
But the main db file can just be opened by double clicking on it. I have
checked that
1.the 'Admin' doesn't belong to 'Admins'
2. My db as an object is not owned by Admin but by the new administrator
that I created. This new administrator is the only member of 'Admins' group.
3. The group 'Users' have not been assigned any permissions by me.
I am using Access 2003 but when I open this db, it says: my db (database:
Access 2000 file format). I wonder if this file format has to do with
malfunctioning of the wizard. To add to confusion, I have used wizard on the
same computer to secure a db which was secured correctly. One change from the
time when wizard was working has been that after I click on 'Finish' button
in wizard, it takes an unusually long time to print the 'One-Step Security
Wizard'; actually it kind of hangs after I click 'Finish' and it has to be
prompted by moving the mouse and then the hourglass symbol appears and then
shows the report after a few minutes. Then it doesn't even display any
message to remind me to close Access as outlined in Step 31 of the same
document that I mentioned above.
Is my wizard broke or am I doing something wrong here. Help would be much
appreciated.
 
What I figured out in the meanwhile is that I can secure my database by
removing the 'open/run' permission in the 'database' object from the 'Users'
group. When I do this, it does let me open the db through the system.mdw. And
the shortcut is still working fine. I am guessing this is what has been
happening: When I was trying to open the db by itself through system.mdw, it
was trying to open the 'Admin' account by default and since 'Admin' is a part
of 'Users' (as is any other user) and 'Users' was lying there being permitted
to 'open/run' the 'database', the database got opened. But this solution has
posed another problem though: I had not given any permission to the users
that I created in my 'Users' group eg. user1, user2 and since I have now
taken away the permission from 'Users' to 'open' the 'database', it also took
away the permissions from user1, user2 to open my database even if they
supplied the correct username and password on logon prompt. Now I have had to
give my users (user1, user2) permission individually to be able to open the
database. Is this a norm or am I still missing something... I remember that
the first time my wizard worked in correctly securing a database, I didn't
have to take any of these additional steps. What could have I possibly done
wrong that the wizard was not able to secure my db in the same way that it
did initially.
 
I give up!

I've told you why it is not working. You are not following an explicit
list of written instructions.

Get the Access Security FAQ, often referenced in this newgroup. Then
follow every step, in sequence, ADDING AND OMITTING NOTHING.

TC
 
Back
Top