Workgroup information file problem

[CB]

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

 

[Chris O'C via AccessMonster.com]

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]

Hi Chris,

Comments below...

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).

Whew, that was literally a weight off my shoulders when I read the above
paragraph! I can now enjoy the rest of my evening. I couldn't wait until
tomorrow to see if a reply was posted. It was not clear to me that the
workgroup shown was the permanent workgroup joined to. Thanks for pointing
that out! I should be okay then.

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"

Great! I'll try that tomorrow.

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.

I don't believe I used the security wizard. Weird comment, huh? I created
the database for one company in 2001 and they laid me off in 2003. I've been
away from Access since then. I am now at a second company that needed a
database pretty much like the one I already created for company one. Rather
than reinventing the wheel, I call up company one and they gave me permission
to use the database that I created for them. I have since modified it a great
deal for company number two. Got that?

Anyway, I don't remember using the security wizard. Since then, I've done a
lot of playing around with the various permissions on various objects. This
includes ensuring that the "Users" group has ZERO permissions and that
"admin" is a member of only this 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.

Sorry about that. I don't hold down the shift key until I press "OK" after
entering my username and password. I presume this is the same as holding down
the shift key while double-clicking on the shortcut.

I didn't realize that holding down the shift key while double-clicking the
filename would open the database with the SYSTEM.MDW (permanent workgroup).
Hmm, since "admin" has ZERO permissions, I'm thinking they still couldn't
access the database. Is this right? I'll have to try that tomorrow.

Chris
Microsoft MVP

Thanks again, Chris!

Chris - as in the NOT Microsoft MVP - obviously

 

[CB]

Comments below...

Hi Chris,

Comments below...



Whew, that was literally a weight off my shoulders when I read the above
paragraph! I can now enjoy the rest of my evening. I couldn't wait until
tomorrow to see if a reply was posted. It was not clear to me that the
workgroup shown was the permanent workgroup joined to. Thanks for pointing
that out! I should be okay then.



Great! I'll try that tomorrow.

I just tried it and all is okay. Whew, I'm happy to know my security is
working as planned.

I don't believe I used the security wizard. Weird comment, huh? I created
the database for one company in 2001 and they laid me off in 2003. I've been
away from Access since then. I am now at a second company that needed a
database pretty much like the one I already created for company one. Rather
than reinventing the wheel, I call up company one and they gave me permission
to use the database that I created for them. I have since modified it a great
deal for company number two. Got that?

Anyway, I don't remember using the security wizard. Since then, I've done a
lot of playing around with the various permissions on various objects. This
includes ensuring that the "Users" group has ZERO permissions and that
"admin" is a member of only this group.



Sorry about that. I don't hold down the shift key until I press "OK" after
entering my username and password. I presume this is the same as holding down
the shift key while double-clicking on the shortcut.

I tried this too. I have to hold the shift key when I press "OK" otherwise,
I have little access to the menus (as for other users).

I didn't realize that holding down the shift key while double-clicking the
filename would open the database with the SYSTEM.MDW (permanent workgroup).
Hmm, since "admin" has ZERO permissions, I'm thinking they still couldn't
access the database. Is this right? I'll have to try that tomorrow.

Holding the shift key while double-clicking on the filename is no different
than simply double-clicking the filename. The user is told that they don't
permissions and to contact the administrator.