Associate dbs with security file

[agfon]

I have an unsecured frontend which I would like to associate with an existing security file (mdw).

How would I go about reseting the frontend to be dependent upon the mdw file? I would like it to be set up so that it requires a link to be used and a username and password.

It's not enough just to set-up the link because the user can still open the frontend directly. I want the user to be prevented from opening the frontend unless it's via the link.

I would appreciate any feedback.

-Fred

 

[lupins46]

You have to read a lot more about Access workgroup security I'm afraid.
The workgroup login just authenticates you as a user. To control what each user can do in a database you must go through each object in the database and define the permissions for each user group.


You can find a good and straightforward description of Access security here:

http://www.geocities.com/jacksonmacd/AJMAccessSecurity.pdf

Do not practice on anything that matters!

 

[agfon]

Thanks lupins-46.

Actually, I'm not trying to define the permissions for each user group. This has already been done and is stored in the security (mdw) file.

When creating the dbs from scratch, you can use the security wizzard to set up a new security file. Thus, you have to provide a username and password to open the dbs.

But what if you already have a security file from another dbs and you want to associate your new dbs with it? I managed to set up a link which opens the new dbs using the mdw file. However, anyone can open the new dbs directly by simply double-clicking on it.

What would I need to do to set-up the new dbs so that if the user is prevented from opening it directly?

Thanks.

 

[lupins46]

'Actually, I'm not trying to define the permissions for each user group. This has already been done and is stored in the security (mdw) file.'

No it isn't.
The permissions are held in the mdb file NOT the mdw file.
The function of the mdw file is purely to establish that you are a valid user (of ANY database).
The mdw is not associated with any mdb file and the mdb file is not associated with any mdw file except when you make that association in the startup command or by joining the workgroup through the workgroup administrator program.

If you use a shortcut that includes the mdw file and the mdb file then the user will get the login prompt.
However, this will not make the database secure. As you have said, anyone who double clicks the database can open it.

 

[eileen1309]

I found a fairly decent article on How to User Microsoft User Lever Security that may answer some of your questions.