Access Security issue - Part 2

[ThriftyFinanceGirl]

So the issue that I inherited is this:

*There is a large group of users using databases that have been secured
using an Access MDW
*There is another group of users that are not a part of this group.
*The users for the new database are a COMBINATION of users from one
workgroup and users that are not a part of any workgroup.

1. Again why do the users of the workgroup have to log in to "my"
application -- even though I have not (and am not) going to use Access
security to secure my application.
2. The issue has been brought up that, if you are using Access security,
you can only be a part of one workgroup? So even if I WAS going to implement
Access security for "my" application, what would be the point?
3. I have been pointed to having my users use a large shortcut pointing
them to a different mdw file, however, we don't want to use shortcuts for
these users, we are going to have a split frontend/backend with the backend
in a secured folder that only these people would have rights to, and the
front end on their computers so that we can push versions easily. We have
also thought of pushing our app out through Citrix as well.

I really need some good answers here guys! Any Access Security Police out
there?

 

[Douglas J. Steele]

If Access has been associated with a different workgroup that the default
system.mdw (and security was set up properly for that other workgroup),
you're going to have to log into Access. That's because properly implemented
security will have removed the Admin id from the Admins group. If you start
without logging in, you'll be Admin, but won't have any permissions.

While there is an option to use the Workgroup Administrator, there's no
reason to use it. Instead, keep associated with the default system.mdw, and
use a shortcut that associates the specific MDB (or MDE) with the correct
MDW file.

 

[ThriftyFinanceGirl]

Douglas...

Let me get this perfectly straight...

so

1. Access should have been still associated with the default mdw
2. When security is set up right (in a copy mdw) then the Admin ID has been
removed from the Admins Group (which is correct if done in a copy mdw)
3. Then the database only should be pointed to the mdw that has the security
set up not Access itself.


Last question ... So how to fix the issue now? Meaning how do we
"reassociate" Access with a default system.mdw? And then we just use the
shortcuts with the MDB's that need to be secured through that workgroup?

 

[Douglas J. Steele]

You need to use the Workgroup Administrator tool to change the associated
workgroup back to the default mdw.