Access 2003 Workgroup File

[Anthony Bollinger]

My directory Application Data\Microsoft\Access has two workgroup files,
System.mdw and System1.mdw. Both have modified timestamps. How can I tell,
for a given Access 2003 database, which is the associated workgroup file?

Thanks,
Tony

 

[Peter Yang[MSFT]]

Hello Anthony,

I understand that you'd like to know the associated workgroup file for a
given database. The default mdw file is actually user profile based. If a
Windows user joins a workgroup file, Access will open all database by using
the same workgroup file if you log on as that Windows user.

The default workgroup file is Application Data\Microsoft\Access\system.mdw
file. If you open the mdb file directly, the system.mdw is used by default.
However, if you once joined a different workgroup file, it will open that
workgroup file as default. You could check this after you open the
database, click Tools->Security->Workgroup administrator.

If you'd use a different workgroup file, you can create a desktop shortcut
that uses the appropriate workgroup file for that session.

The target of the shortcut would look like"path to msaccess.exe" "path to
mdb" /wrkgrp "path to secure mdw". For example:

msaccess c:\test\db1.mdb /wrkgrp c:\test\system.mdw

Please see the following articles for more details:

Q289885 ACC2002: Overview of How to Secure a Microsoft Access Database
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q289885

305542 Understanding the role of workgroup information files in Access
security
http://support.microsoft.com/?id=305542

Frequently Asked Questions About Microsoft Access Security for Microsoft
Access versions 2.0 Through 2000
http://support.microsoft.com/support/access/content/secfaq.asp

If you have any further questions on the issue, please feel free to let's
know. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Joan Wild]

Technically speaking, a database can be associated with more than one workgroup file.

The mdw is associated with the session of Access, not a specific mdb file.

Access ships with a workgroup named system.mdw, so that one is likely the original one, however it could have been modified.

If your 2003 database was secured properly, i.e. with the intent that it is only useable with one secure mdw, then you should only be able to open it while using the correct mdw file.

You can create desktop shortcuts to test out each mdw file - one of them should give errors, the other one should prompt for username/password.

"path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw"

 

[Peter Yang[MSFT]]

Hello Tony,

I'm still interested in this issue. If you have any comments or questions,
please feel free to let's know. We look forward to hearing from you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

======================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

 

[Anthony Bollinger]

Thank you. I am still working on it. May be after the holiday. I am still
doing some reading to understand [1] the best setup for a C/S setup where
the data mdb resides on a file server and the front end mdb is on a few user
desktops (about 2-5), and [2] trying to understand how a power user would
not be able to break the security by supplying a different mdw file. I am
reading the available online resources, but if you have any input, it would
be most welcome.

Thanks!
Tony

 

[Rick Brandt]

Thank you. I am still working on it. May be after the holiday. I
am still doing some reading to understand [1] the best setup for a
C/S setup where the data mdb resides on a file server and the front
end mdb is on a few user desktops (about 2-5), and [2] trying to
understand how a power user would not be able to break the security
by supplying a different mdw file. [snip]

Because a properly secured file can only be opened with the correct MDW file.

 

[Joan Wild]

All mdw files share some things in common - the Users Group and the Admin User. It is very important that neither of these entities have permissions to anything nor own anything.

The Admins Group however, is different.

That is why you create a new mdw file, and then take the necessary steps to create your own 'super' user and remove everything for the Users Group and the Admin User. It is important to follow the steps exactly, or you can easily find that the Admin User still owns the database (and therefore can get at anything, regardless of their permissions).