Server permissions vs. Access workgroup

  • Thread starter Thread starter Tony
  • Start date Start date
T

Tony

Good morning...I have a BE/FE application that's about
ready to be deployed, but there is still some
considerations. I only created an Access Workgroup once
and everytime I wanted to create a new database, I was
asked for a username and password. Question: Can I
create a workgroup ONLY for the database in question? I
created a login form in this database and I was going to
use the network's permissions. Any advices would be
appreciated. Thanks.
 
Yes, workgroups can be specific to a database.

Use the Workgroup Administrator program (Wrkgadm.exe) to switch you back to
your original system.mdw. Then, create a shortcut to your secured
application that explicity points the the workgroup file associated with it:

"full path to msaccess.exe" "full path to MDB file" /wrkgrp "full path to
MDW file"
 
Tony said:
Good morning...I have a BE/FE application that's about
ready to be deployed, but there is still some
considerations. I only created an Access Workgroup once
and everytime I wanted to create a new database, I was
asked for a username and password.
Click to expand...

When you create a new workgroup, the workgroup administrator 'kindly' makes
that the default one to use for every session. You can use the workgroup
administrator to join back to the standard system.mdw. Then you'll get no
login prompt.
Question: Can I
create a workgroup ONLY for the database in question? I
created a login form in this database and I was going to
use the network's permissions. Any advices would be
appreciated. Thanks.
Click to expand...

For the secure database, you can use the workgroup administrator to join the
appropriate workgroup, however it is easier to create a desktop shortcut to
launch the secure database. The target would look like
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"

That will override the default workgroup just for that session.

Access security can be broken into, however any scheme you try to create
yourself will be even easier to break. All anyone has to do is create a new
mdb and import all objects from yours.
 
At this point there is no workgroup setup. The BE resides
on the server and I am going to deploy the FE (.mde) to
client workstations. Can I set the workgroup for the
FE.mdb and then make an .mde? Will the workgroup be for
the .mde? I created custom menu bars, so users won't have
access to the standard menu options. thanks
 
Tony said:
At this point there is no workgroup setup. The BE resides
on the server and I am going to deploy the FE (.mde) to
client workstations. Can I set the workgroup for the
FE.mdb and then make an .mde?
Click to expand...

No, you can't do the above, you need to make a shortcut (otherwise, you do
have to join the workgroup..and that effects ALL other databases..and you
don't want to do that...).

Also, since new users, and security might be changed, then obviously the
workgroup will be in the same location as the back end...
 
Back
Top