security - is my db unsecured? 1

[mguwc]

I have a database that I created with microsoft access 2002. I have joined a workgroup, that when I work on my computer it asks me for a password. I have assigned the staff that will be using this db passwords and permissions. The frontend is on their hard drive and the data (backend) is on the network. This unit has different versions of Access (2002 and runtime) on different machines. When I put the db BE and FE on the full Access, it works as it should, prompting for a login. When I put the db BE and FE on runtime machines, the db just pops up and does not ask me for a password.

I have looked though the threads and nothing seems to help. Is there something I am overlooking??????


- Maria

 

[LittleSmudge]

Firstly - in you security set up you've overlooked taking away all the privlidges from the Admin user

Secondly in the machines where it currently doesn't ask for a password you have not associated MSAccess with the appropriate security.mdw file.

My preferred approach is to use a desktop shotcut for the database and have the shortcut target in the following for

"\\server\path\Access.Exe" "\\server\path\database.mdb" /wrkgrp "\\server\path\security.mdw"

That will force the database to use the appropriate security.mdw file.



'ope-that-'elps.



G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.

 

[mguwc]

Thank you for all your help.

1st - my database was not secured. Therefore, I needed to go in a create a new workgroup. The only problem I had and I'm not sure if others have had it..... is that in ACCESS 2002 and maybe in other versions, when you go in and create a new user and remove the default admin user from the ADMINS group you have to make sure that before doing so, you establish permissions for all objects for the NEW admin user. I was not doing this and everytime I performed my security wizard, nothing happened. This is because the default Admin user and the NEW Admin user had no ADMIN group permissions. The ADMIN group does not have permissions.

So after figuring this out, and establishing the necessary permissions and removing the permissions for the default ADMIN....I ran my security wizard and everything worked as it should.

2. The way you told me to go in through the shortcut and force the workgroup for runtime worked perfectly. Thank you again.

- Maria

 

[LittleSmudge]

Oh Yes Maria. You will not be the first - or last - person to fall over that one.

It is quite possible to remove administrator privlidges from every user and group in the security file.

Your database is then 'stuffed' because there is no-one with the rights to add permissions back in again.

That is one of the reasons why the first step in securing any database is:-

"Take a complete backup copy of the unsecured version."



;-)



G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.