Re: Workgroup information file problem

Tech-Archive recommends: Fix windows errors by optimizing your registry



You should be permanently joined to the system.mdw file so you don't have to
supply a user name and password every time you open an Access db. If you use
the workgroup administrator to check which workgroup you're joined to, that
only shows which workgroup you're *permanently" joined to, not the one being
used for the current session (which you indicated in your shortcut).

To check which workgroup is being used for the current session push ctrl+g to
open the immediate window. Paste this and push enter:

? syscmd(acSysCmdGetWorkgroupFile)

If you opened the db with your shortcut the path shown will be "\\...network
path to…\Eqpt_Cal.mdw"

If you used the Access 2K security wizard to secure the db, it's probably not
secured. That wizard has a bug. You need to do additional things to make it
secure, like remove permissions from the users group.

It's not clear what you did to "bypass the startup". Did you hold down the
shift key while double clicking on the file name instead of the shortcut?
That will open the db while joined to the permanent workgroup. Or did you
hold the shift key while double clicking on the shortcut? That will open the
db while joining you to the workgroup listed in the shortcut for the current
session.

Chris
Microsoft MVP


CB wrote:
Hi all,

I am confused!!!!! Something came up when I was installing the front end and
short-cut on a computer in our lab.

I have a split database that employs USL. FWIW, the user “Admin” only
belongs to the Users group and that group (and user) has zero permissions,
i.e., that user can’t even open the database. I “own” the database and every
object in it. I am the only user in the Admins group.

Additionally, I’ve removed virtually all access to the menus in MS-Access
(though I haven’t yet disabled the ability to bypass the shift key). The
shortcut to open the database has the following target.

"C:\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\Documents and Settings\All
Users\CalDatabase\Eqpt_Cal2003FE.mde" /Wrkgrp "\\...network path
to…\Eqpt_Cal.mdw"

When I select the short-cut, I’m prompted for my username and password. So
far, so good.

I decided to bypass the startup so I had full access to the menus. Then,
something in the back of my mind prompted me to ensure that I was joined to
the proper workgroup. I was joined to the SYSTEM.MDW workgroup! (I didn’t
catch this on my machine because at some point I set Eqpt_Cal.mdw as the
default workgroup file so all appeared to be going well! I'm not even sure
when I did that. Sheesh...)

Anyway, when I look at the user and group accounts and their respective
permissions, I see all the new users I created and all the permissions I
assigned to the various groups. I thought perhaps there was a VERY slight
chance that I accidently modified the SYSTEM.MDW file so I copied another
SYSTEM.MDW file over from another machine. I see the same thing. What
gives??????? I would have expected that if I were joined to that workgroup, I
would see only the default users and their permissions.

FWIW, my database was originally created in Access 2000 and I recently
converted it to Access 2003. Per the Security FAQ, I should still be able to
use my WIF created in A2000 but would this be causing any issues?

I have more questions but have to call it a day.

Thanks for any and all help!

Chris

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200809/1

.



Relevant Pages

  • Re: security only works on my PC
    ... I rejoined the system.mdw workgroup and set up the shortcut ... I had already removed permissions from the users ... click on Join and rejoin the system.mdw. ...
    (microsoft.public.access.security)
  • Re: Location of Workgroup administrator in Office 2002
    ... in the same folder. ... You shouldn't have multiple users sharing the same mdb. ... > shortcut to test the databse on my C drive the only difference being ... >> while using the system.mdw workgroup file. ...
    (microsoft.public.access.security)
  • Re: Workgroup information file problem
    ... the workgroup administrator to check which workgroup you're joined to, ... used for the current session (which you indicated in your shortcut). ... database pretty much like the one I already created for company one. ... lot of playing around with the various permissions on various objects. ...
    (microsoft.public.access.security)
  • Re: Old Question, new twist: No read definitions
    ... I am unable to change any permissions at all, ... > Workgroup ID: JCInc ... Given what I see in the above, the 'original WIF' doesn't exist anymore ... If you don't have a shortcut, then create one with the above in the target. ...
    (microsoft.public.access.security)
  • Re: Identical user names, different DB
    ... > shortcut was to direct you to the correct wrkgroup file. ... Actually the workgroup administrator does not tell you the current workgroup ... mdw files do. ... > opens right up. ...
    (microsoft.public.access.security)