Workgroup File in MS Access 2003

  • Thread starter Thread starter Roshan Abbasi via AccessMonster.com
  • Start date Start date
R

Roshan Abbasi via AccessMonster.com

I created a Workgroup file (Project.mdw), assigned different Permissions to
different Groups, and put different Users in appropriate Groups.
The above setup is working fine and just as required. But, if I remove or
rename the Workgroup file, MS Access does not look for it, creates in its own
Workgroup file and starts just as usual - without asking for the Password, or
caring about the Permissions and/or restrictions set.
How can I make the database file bound to the MDW file, so that it does not
open without it.
 
Roshan Abbasi via AccessMonster.com said:
I created a Workgroup file (Project.mdw), assigned different Permissions to
different Groups, and put different Users in appropriate Groups.
The above setup is working fine and just as required. But, if I remove or
rename the Workgroup file, MS Access does not look for it, creates in its
own
Workgroup file and starts just as usual - without asking for the Password,
or
caring about the Permissions and/or restrictions set.
How can I make the database file bound to the MDW file, so that it does
not
open without it.
Click to expand...

A database file is not bound to any mdw file. The mdw file affects the
Access session. In fact you can have a secure mdb that uses more than one
mdw (although not likely it is possible). Also the reverse is true - many
mdb files can use one mdw file.

Every time you use Access, it uses a workgroup file (system.mdw by default).
From your description above, I gather that you had joined your project.mdw
as the default? That would cause the login prompt to appear every time you
opened a mdb (regardless of whether it was secure or not).

When you moved/renamed it, Access couldn't find it's default mdw, and so it
creates a new system.mdw. Since the Admin user in this mdw does not have a
password set, you get no login.

And here's the most important point. Since you are able to open your secure
mdb using a standard system.mdw, then you missed a step in securing it.
This is actually a good way to test if you've implemented security
properly - you should not be able to open your mdb, unless using the proper
mdw.

Follow every step outlined in the Security FAQ
http://support.microsoft.com/?id=207793

Security Whitepaper
http://support.microsoft.com/?id=148555

I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm
 
I have tried to understand and practiced according to the information stated
in the links forwarded by Joan Wild, especially his very straight-forwardly
mentioned steps at www.jmwild.com/AccessSecurity.htm.

Unfortunately, nothing seems helping. Apparently, I have performed all the
necessary operations completing in the following steps:

(1)- Created an MDW file.
(2)- Created User & Group Accounts.
(3)- Added New User (only One) to the 'Admin 'group.
(4)- Removed 'Admin' from the 'Admins' group.
(5)- Set Password for the default 'Admin' user.
---------------------------------------------------
(6)- Re-started MS Access with the 'NewAdmin' user .
(7)- Set the Password for the 'NewAdmin'.
(8)- Created 'Full Permission' & 'Read-Only Groups'
(9)- Set 'Users-group' have No permissions.
(10)- Added New Users
(11)- Put "User1" into 'Full Permissions' group.
(12)- Put "User2" into 'Read-Only' group.

It will be great help, if someone can point out, where I have gone wrong,
please.
 
Roshan said:
I have tried to understand and practiced according to the information
stated in the links forwarded by Joan Wild, especially his very
straight-forwardly mentioned steps at
www.jmwild.com/AccessSecurity.htm.

Unfortunately, nothing seems helping. Apparently, I have performed
all the necessary operations completing in the following steps:

(1)- Created an MDW file.
(2)- Created User & Group Accounts.
(3)- Added New User (only One) to the 'Admin 'group.
(4)- Removed 'Admin' from the 'Admins' group.
(5)- Set Password for the default 'Admin' user.
---------------------------------------------------
(6)- Re-started MS Access with the 'NewAdmin' user .
(7)- Set the Password for the 'NewAdmin'.
(8)- Created 'Full Permission' & 'Read-Only Groups'
(9)- Set 'Users-group' have No permissions.
(10)- Added New Users
(11)- Put "User1" into 'Full Permissions' group.
(12)- Put "User2" into 'Read-Only' group.

It will be great help, if someone can point out, where I have gone
wrong, please.
Click to expand...

The first place you have "gone wrong" is that you never stated what your
problem is.
 
My problem is stated in my first posting of this thread:-)
Anyhow, just to repeat, if I remove or rename my WPG file, my database file
does not look for it and uses its default system.mdw. Consequently, the
Permissions and Restrictions can not be applied.
I hope to find some solution to this problem.
 
Roshan Abbasi via AccessMonster.com said:
I have tried to understand and practiced according to the information
stated
in the links forwarded by Joan Wild, especially his very
straight-forwardly
mentioned steps at www.jmwild.com/AccessSecurity.htm.

Unfortunately, nothing seems helping. Apparently, I have performed all the
necessary operations completing in the following steps:

(1)- Created an MDW file.
Click to expand...

Did you join this by default or did you create a shortcut to ensure you were
using this mdw?
(2)- Created User & Group Accounts.
(3)- Added New User (only One) to the 'Admin 'group.
(4)- Removed 'Admin' from the 'Admins' group.
(5)- Set Password for the default 'Admin' user.
Click to expand...

You would create a new database at this point and import all the objects
from your mdb; this ensures that NewAdmin owns all the objects.
 
Hi,


Sounds you use the default system.mdw, the one everyone get right out of the
box. You have to start with one you create. From the menu, Tools | Security
| Workgroup Administration ... [ Create ]


If you use the default system.mdw, anyone can REPLACE IT with the original
one which, as you know, has no password for Admin, and let every one enter
without any challenging prompt for identification and supplying password.

That is a common mistake, in fact, it is in the FAQ.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q165009 :
-----------------------
• I thought I secured my database, but someone opened it with his or
her own workgroup file. Is Microsoft Access security broken?

-----------------------

You may find more appropriate to ask further relevant questions in the
Access newsgroup dedicated to security.


Hoping it may help,
Vanderghast, Access MVP
 
Back
Top