Back End Security Flaw

[Guest]

Hi all,

I have created a custom workgroup file that I named CogGroup.mdw.

I then joined my split frontend to CogGroup.mdw and that works fine, but
when I join the backend to CogGroup.mdw then the default workgroup file for
Access 2003 also changes over to CogGroup.mdw.

If I open Access without opening a database and change the workgroup back to
the default "System.mdw" then the backend also gets changed to "System.mdw".

This seems to only affect the backend file. Has anyone else experienced this?

-A

 

[Guest]

You misunderstand how workgroup files work.

Access always has some workgroup set as the default. This one is used for
all sessions of Access. It is set via Tools, Security, Workgroup
Administrator.

You can over-ride this default by using a desktop shortcut that uses the
/wrkgrp switch to specify a different mdw to use, for that session.

You do not 'join' a database to a workgroup file.

 

[Rick Brandt]

Hi all,

I have created a custom workgroup file that I named CogGroup.mdw.

I then joined my split frontend to CogGroup.mdw and that works fine, but
when I join the backend to CogGroup.mdw then the default workgroup file for
Access 2003 also changes over to CogGroup.mdw.

If I open Access without opening a database and change the workgroup back to
the default "System.mdw" then the backend also gets changed to "System.mdw".

This seems to only affect the backend file. Has anyone else experienced this?

If you can open the back end with System.MDW then it is not secured properly.
You have a basic misunderstanding of how Access security works. The file you
are opening does not dictate or have a "link" to a particular MDW. The MDW is
chosen by the session and whether you can open a specific file is determined buy
the ownerships and permissions in the file.

When you open a file using System.MDW then you are doing so as "Admin" member of
"Users". Neither of these should be able to open a properly secured file.

 

[Guest]

Hi Joan,

Thanks for your reply. What I'm trying to do is secure both the frontend
and backend files and have them both use the CogGroup workgroup. At the same
time I need Access to keep it's default workgroup so I can open other
databases without being prompted for passwords. Is this possible to do?

-A

 

[Joan Wild]

Yes. You secure both FE and BE using CogGroup. Then ensure you are joined
by default to system.mdw (at this point you could check to make sure that
you can't open either mdb; if you can, then you didn't secure them
properly).

Access will use this default system.mdw for every session, and there will be
no login prompt.

For your secure database, use a desktop shortcut the over-rides the default
workgroup. The target would look like:

"path to msaccess.exe" "path to frontend" /wrkgrp "path to CogGroup.mdw"

 

[Guest]

Joan,

Thanks again for your valuable input. I think I'll follow the example you
used in the post "How to secure a split db" to secure both frontend/backend.
Without you I would be screwed

-A