FE / BE Security Groups

[David Eagar]

For a little light relief I thought I would delve into the joys of security groups and immersed in searches and reading material. From what I have learnt so far, yes FE / BE best approach and take time, as obviously easy to get wrong and difficult to undo.

Not looking for the answer, just a hint that I'm on the right track

The FE groups settings is where the bulk of the detailed work is required?
The BE groups settings are to ensure the correct read / write access to the tables?
I am thinking of making FE groups as BE users (smart or dumb) to simplify this end?

Any encouragement / early warnings appreciated

 

[David Eagar]

Related question - I have 4 or 5 databases, I switch security on for 1, I switch them on for them all? Yes/No

 

[Guus2005]

Related question - I have 4 or 5 databases, I switch security on for 1, I switch them on for them all? Yes/No

No.(when they are not replicated databases)

 

[Guus2005]

For a little light relief I thought I would delve into the joys of security groups and immersed in searches and reading material. From what I have learnt so far, yes FE / BE best approach and take time, as obviously easy to get wrong and difficult to undo.

Not looking for the answer, just a hint that I'm on the right track

The FE groups settings is where the bulk of the detailed work is required?
The BE groups settings are to ensure the correct read / write access to the tables?
I am thinking of making FE groups as BE users (smart or dumb) to simplify this end?

Any encouragement / early warnings appreciated

There are no BE users. Only FE users. Your FE has no tables. The only tables you see are linked to the BE. The BE has only tables (perhaps a single macro, perhaps some code) nothing more.

All the users in your new workgroup don't have any permissions in your BE.
In your FE, all the permissions are group based. The users are member of a group.
Don't know how far i should go with this.

Have phun!
HTH

 

[David Eagar]

After a lot of trial and very much more error, I am owner of the database and can do everything - created Groups to limit availability of data and tried to create a new user linked to a Group

Failed miserably - user cannot open any form

I will keep struggling, but if any kind soul wishes to help me set up the Groups and link users to specific groups, feel free and much appreciation if you do

To Guus2005, so having run the Security Wizard, why do the other 4-5 databases now ask me for a user name & password?

 

[David Eagar]

Struggles mostly successful - but I am sure there is in easier way to assign Group permissions than the way I am doing it

 

[Guus2005]

After a lot of trial and very much more error, I am owner of the database and can do everything - created Groups to limit availability of data and tried to create a new user linked to a Group

Failed miserably - user cannot open any form

I will keep struggling, but if any kind soul wishes to help me set up the Groups and link users to specific groups, feel free and much appreciation if you do

To Guus2005, so having run the Security Wizard, why do the other 4-5 databases now ask me for a user name & password?

There is one system.mdw file don't know where it resides but you should use the workgroup manager to create your own workgroup file. Preferable not called System.mdw.

With this new workgroup file you can create your own databases. These newly created databases now look for this new workgroup database and not the default System.mdw.

Having done that, every database should open the way they used to.

So reset the Admin password on the default System.mdw and create a new one!

 

[statsman]

When you set up security in Access, the security settings (User IDs, Passwords and Permissions) are saved in a file called System.mdw

System.mdw normally resides in the Windows/system folder on your computer.

The System.mdw on my computer is different than the System.mdw on your computer. If your database is on my computer and my System.mdw has no Access security settings, it lets me right in with no challenge.

The way to go is to create a new .mdw file (different name) which is in the same folder as the database. You have to place this new .mdw in the path on your shortcut to the database so that anyone who opens the database will have to enter their UserID and Password.

Don’t forget to return the settings to System.mdw when you close the database.

For an excellent overview of Access security, go to:
http://www.geocities.com/jacksonmacd
download the first file – Security Paper by Jack Macdonald. It’s a little long but it tells you everything you need to know.

 

[David Eagar]

Thanks for the tips, got it mostly working now. Still a little uncertain on multiple databses. Can each db have its own system.mdw file?

 

[Guus2005]

Sorry, but this is not correct.

...
The System.mdw on my computer is different than the System.mdw on your computer. If your database is on my computer and my System.mdw has no Access security settings, it lets me right in with no challenge...

They are exactly the same. Otherwise it would be useless to post any example databases here.
That's why you should create your own workgroup file. Preferable with a different name than System.mdw.

Using a shortcut you can set the commandline parameters to open you protected database with a different workgroupfile.

Enjoy!
HTH

 

[David Eagar]

Make up your minds! - I am an ameteur, do I or don't I?

 

[statsman]

Thanks for the tips, got it mostly working now. Still a little uncertain on multiple databses. Can each db have its own system.mdw file?

System.mdw is the default location to store your security settings.

If you use SYSTEM.MDW to store your security settings then all of the databases on your computer will require a log in and password.

If you use a different .mdw for each database the you can tailor the security settings for each database.

I would leave the SYSTEM.MDW as is with no security settings. Those databases you do not require security for will not require a login or password.

The databases you want security on will then require a new .mdw file for each one and you can tailor the security as required.

Its set up slightly differently if you're in a network.

 

[statsman]

Sorry, but this is not correct.
They are exactly the same. Otherwise it would be useless to post any example databases here.
That's why you should create your own workgroup file. Preferable with a different name than System.mdw.

Using a shortcut you can set the commandline parameters to open you protected database with a different workgroupfile.

Enjoy!
HTH

My fault for being unclear. If you have set up a security system and stored it to System.mdw, then my System.mdw file is now different than yours. That means that if you transfer your secured database onto my computer, my computer will not prompt for a login.

 

[David Eagar]

Still battling, but making progress - I have one issue that is bugging me & I can't put my finger on the cause (other than me being a klutz)

Created the new workgroup file and stored it in a new directory in C (away from my Documents & Settings) make changes to Startup settings and works fine, until I restart my computer and it reverts to orginal settings again

Any hints most welcome

 

[Dennisk]

When you start Access it always uses the system.mdw. Use the workgroup manager to join the workgroup of your choice.

 

[David Eagar]

I think that's the bit that's bugging me - yes, followed the instructions and joined the workgroup - I know this works (we have several at work set up by experienced users and it works perfectly) it just doesn't seem to want to work for me.
I thought making sure it was not linked to my Documents and Settings would have made it foolproof. Just made a fool out of me

 

[rhett7660]

Also make sure the permissions are set on the folder if the folder has security settings/permissions assigned to it. That can also play havic on your security settings...

 

[David Eagar]

Yep, checked all that early in the peice - I would think that if it were folder security, it would not let me make the changes in the first place