Access MDW file problems

[SJ]

Hi hope someone can help

We have a shared network drive on an SBS2003 server. We have a new Access
database which is split into 2. One database contains just the data tables,
and is situated on the shared network drive within its own folder. Each
user has a copy of the system database within a folder on their local C
drive.

We have had issues of some users getting "no read permissions on tablename".
i have eventually tracked it down to the fact that some users, including
myself, are joined to an old .mdw workgroup file that is also on our network
drive (although in another folder), and if the users are joined to this
file - there are no problems. If they are not joined to this mdw workgroup
file, and are linked to their own local system.mdw file, then they have
probems.

OK need to sort it out, so have a few questions:

1. With a shared database on the network, is it necessary/preferable to have
the common mdw workgroup file. It was set up many many moons ago.
2. If so, how do I add more users - I thought it was a file wrkgrpadmin, but
cant seem to find the file anywhere.
3. If its not necessary to have common mdw workgroup file, and have users
join; how do I set my database so that it will allow the users to use their
own local system mdw file?

4. As a matter of interest, how would the database have got linked to this
common mdw workgroup file. Was is that because I was already joined to the
workgroup when i created/modified the database it became associated?

thanks
Alex

 

[Keith]

1. With a shared database on the network, is it necessary/preferable to
have the common mdw workgroup file. It was set up many many moons ago.

If you have set up user-level security correctly then it is essential to
have your custom WIF (*.mdw) on the server in a public location (with your
backend file is an ideal place). Your default PC setting should be to an
unmodified "system.mdw" which ships with Access. You would switch to your
custom WIF using the "/wrkgrp" command line switch in a shortcut to your
mdb. This way, 'unsecured' mdb files can be opened directly.

2. If so, how do I add more users - I thought it was a file
wrkgrpadmin, but cant seem to find the file anywhere.

You would add more users from the Tools/Security menu item. The Workgroup
Admin tool is for managing WIFs.

3. If its not necessary to have common mdw workgroup file, and have
users join; how do I set my database so that it will allow the users to
use their own local system mdw file?

As previously stated they do not have to 'join' - the preferred method is
to use a shortcut to your db and the "/wrkgrp" switch in the command line.
Typically: "Path to Access.exe" "Path to your app.mdb" /wrkgrp "Path to
your mdw" - including the quotation marks.

4. As a matter of interest, how would the database have got linked to
this common mdw workgroup file. Was is that because I was already
joined to the workgroup when i created/modified the database it became
associated?

It sounds as if user-level security may not have been correctly implemented
in the first place, resulting in the hybrid situation you seem to be
describing. I find it best to start Access using a shortcut to my secured
app and then managing security from there. If you manually switch to your
custom WIF you might forget to switch back when you've finished.

HTH - Keith.
www.keithwilby.com

 

[SJ]

Hi Keith - thanks for your post

Ok I have set up as suggested, so now everyone starts the database from a
shortcut on the desktop which switches them to the custom mdw file on shared
server.

I have checked my own account and have rights to all objects, yet if i try
and change an object and save e.g .a query, I get error message saying that
I dont have sufficient rights !

Help!