work group file problems

[pablavo]

First of all, I'll tell a bad joke...

What's green, has four legs and falls from trees? (answer at bottom)

I've made a workgroup file for security and have the backend file on the server, and I want to deploy the frontend to all the PC's. however, I'm not really sure how to deploy the frontends so that they use the workgroup file.. When I deploy the frontend to the PC's, anyone can access the DB without the workgroup file (which is on the server).

How should I do this? Do I have to go to all PC's and overwrite the default workgroup file and put the workgroup file I've made in plcace of this? There's got to be an easier way.
Help me. please!


Joke continued...

a snooker table hehe

 

[Sum Guy]

Going by this post and your previous one (answered by Gemma) it sounds as though you are using the default workgroup - System.mdw as your workgroup file.
Each database where you wish to have security should have its own workgroup file (don't name it System) saved in the same folder as the back end of the database.

When you install the back and front ends, you place the .mdw for that database in the shortcut. This way, all persons trying to log on will receive a username and password challenge.

If you use the default - System.mdw all of the databases on your computer will demand a user name and password, even though they have not been "secured".
As System.mdw resides in the C:Windows/Settings of your computer, the database on the network will only be secured on your computer.

 

[Guus2005]

Going by this post and your previous one (answered by Gemma) it sounds as though you are using the default workgroup - System.mdw as your workgroup file.
Each database where you wish to have security should have its own workgroup file (don't name it System) saved in the same folder as the back end of the database.

When you install the back and front ends, you place the .mdw for that database in the shortcut. This way, all persons trying to log on will receive a username and password challenge.

If you use the default - System.mdw all of the databases on your computer will demand a user name and password, even though they have not been "secured".
As System.mdw resides in the C:Windows/Settings of your computer, the database on the network will only be secured on your computer.

In addition: If i take my System.mdw and use it to open your database, it will be unprotected!

 

[gemma-the-husky]

just to clarify the whole thing

a database and the mdw file work together to determine who can use a dbs By default (ie system.mdw) all users are in user group, and have admin privileges. However, if you create a new mdw file, remove privileges from admin and user group, and add your own passworded groups to allow these privileges, the dbs will not be useable without the new mdw file. just using system.mdw will not run the database, becuase user and admin dont have enough privileges. Be careful to create replacement admin privileges, as modifying syystem.mdw could lock you out of access COMPLETELY

that is why you should never play with the default system.mdw, but always work with a new mdw group.

However once your database is secured to a particular mdw file, you need that mdw file - they are pretty well uncrackable, and not replaceable - eg a mdw file of the same name, still needs to have the same creation id string.

 

[pablavo]

Hi, thanks for all your help on this folks.

I'm actually struggling to understand this. I'll have to get back to you about how I get on once I've worked on it more.

paul

 

[pablavo]

Ok, Let me know if I've got this correct.

I assign permissions for my database, taking away the permissions for admin (including a password for this accout) and replacing this user acount with another (PowerAdmin is something) for the admins group.

Using the security wizard to assigning the permissions to the groups and so that the new owner of the DB becomes PowerAdmin.

Then, once groups and permissions are set, putting the workgroup file (called ProjectsWorkGroup) on the network drive next to the backend file. Then, placing a frontend file on everyones PC along with a shortcut to the workgroup file (that's on the Network), for example in a folder that resides in the C: next to the Frontend.

Would this be correct? I've done tests with creating DB security with a workgroup file (taking away amin and user rights) and if I move the workgroup file that I created to another folder, the DB will open with no password and groups/Permissions set as if it's using the default workgroup file.

I though it would be the case that if I mearly moved it, it just wouldn't let me in to the database, not open with the default workgroup file.

Am I doing the first part correctly?

Thanks and sorry for not really getting this.

 

[Guus2005]

What i missed in your post was that you created a new workgroup file, using this file you started access and created a new database. This new database is now "connected" to this new workgroup file. Simply copying the system.mdw file to ProjectsWorkGroup.mdw is not sufficient.

In the shortcut to open your new secure database, you have to add a path to the new workgroup file. If you leave that part out, it uses the default system.mdw file. If you have already set the admin password with the new workgroup file, you can't open the new database with the default system.mdw file.

The shortcut to open the new database should look something like:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"C:\Test\Projects.mdb" /wrkgrp "C:\SecurityFiles\ProjectsWorkGroup.mdw"

Enjoy!

 

[pablavo]

I don't understand, if you're refering to the fact that I possibly overwrote the default system.mdw when working with a test database only to overwrite that one with a new system.mdw without any passwords and with no WID so that it resembeld the original system.mdw?

I've created a new workgroup file from the workgroup administrator program called ProjectsWorkGroup.mdw. and as I said, created passwords for admin removed admin and created other groups with passwords etc (with the new ProjectsWorkGroup.mdw within workgrup administrator.)

Am I still doing something wrong? I've followd a book and articles on creating new workgroup info files however they don't tell me much about distributing the files over networks especially with the switch "/wrkgrp". where to put files when distributing them. That's the part that's confusing me and that's the part I'm sure I'll be kicking myself when it works.

thanks

 

[pablavo]

Hi

I've just created another test DB, set up the workgroup administrator, set a password for admin created another user, put in admins group, took admin user away from admins group...

Set up the wizard and moved all ownership of objects to the new user and revoked all admin users rights including the default user's rights.

So, now the admin has nothing but a password. And yet when I stick the made up workgroup file (testWG.mdw) and put it in another location from the default location I set it up on at creation, the test DB opens up with no paswords, no users apart from default. It's using the default workgroup?

I don't get this. am I doing something wrong, how can it just open up using the default system.mdw?

At this point I'm pulling my hair out and giving up...

 

[Guus2005]

Don't give up just yet, you're nearly there!
Follow this checklist:

1 - Did you start Access using the new workgroup? (c:\program files\office.....\msaccess.exe /wrkgrp c:\testWG.mdw)
2 - then did you create a new database?
3 - then did you set the admin password?
4 - close the new database, close Access.
5 - double click the new database. Since it uses the default mdw file, you shouldn't be able to open the new database.
6 - create a link: c:\program files\office...\msaccess.exe /wrkgrp c:\testwg.mdw newdb.mdb"
7 - double click the link to open the new secure database. you are asked to enter username and password.

If it doesn't work please post MDW and MDB.

and finally:
Don't be alarmed when you overwrite the default system.mdw file. Everyone who has the same Access version installed could give you a copy of your original system.mdw file.

 

[pablavo]

thanks for all the help folks.

I've made it thus far, having secured the FE so that know one can access the DB directly without the shortcut. Now I'm securing the BE by using a copy of the FE DB as the backend.

I'll let you know how I get on soon.

Paul