Re: MDB 'remembers' old MDW

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Databases do not 'remember', nor are they absolutely tied to any workgroup
file.

The workgroup file is used for a session of Access - any number of databases
can be used during that session.

In addition it is possible for a database to be used while joined to any one
of a number of mdw files.

The mdw defines the usernames/passwords and group memberships. The
permissions are stored in the mdb file with the objects.

It is possible, and from your description likely, that there are identical
users in both mdw files. Therefore, either mdw can be used with the mdb,
except for those instances where a permission in the mdb has been removed
for a user/group. In other words, they may be able to use it, but hit a
permission error on one object only.

The fact that you 'migrated the user details' from the original mdw to the
new one, suggests that the two mdw files have a lot in common.

If you wanted them separate, then you should have created new Group
names/pids in the new mdw and assigned users to those groups. Permissions
are more easily managed if assigned to groups rather than users, which may
be part of your problem here.

I would ensure that the Security2003.mdw doesn't have any Group names in
common with Security.mdw. Change any Group names, and reassign users into
those new groups.


--
Joan Wild
Microsoft Access MVP

Pete wrote:
I have an Access 2003 front-end database that was originally linked to
'Security.mdw'. It was decided to change how the security groups
were setup so a new 'Security2003.mdw' was created, the user details
migrated into this and the new groups assigned.

This has all works fine, but occasionally when we build and publish a
new mde front-end we get permisssion problems. When we look at the
front-end mdb it appears to be linked to the correct
'Security2003.mdw', but when we look at the user and group
permissions, the groups from the old 'Security.mdw' are listed. Going
through the process of relinking to 'Security2003.mdw' seems to fix
the problems, although there is one temporary table (created via a
make table query) that has to have its permissions reset. The MDE
file has the new workgroup file specified in its launch string.

I don't understand how the mdb can 'remember' the old security
groups. The problem is that I am unable to reproduce it consistently
- I have tried opening Access first, checking the workgroup file,
then opening the mdb; opening the mdb from Windows Explorer so that
it starts Acceess. There must be some reference in the front-end.mdb
to this old mdw that I need to remove. I cannot delete the old
'Security.mdw' as there are other databases that use it still (It is
rare for me to open one of these old databases, but when I do I am
careful to check which mdw file is being used when I open one of the
new databases).

Any ideas appreciated.?

Thanks

Peter




--
Peter Schmidt
Ross-on-Wye, UK


.

Relevant Pages

  • Re: Advance Security Issue Part II
    ... The mdb contains the db objects, the object/SID relationships, and the SID ... Read/Insert/Update/Delete permissions on a table or query). ... I can't see a use for the mdw once you've logged in. ...
    (microsoft.public.access.security)
  • Re: User access on a company intranet
    ... Yes they need full permissions on the folder where the backend is. ... You wouldn't need to do this in your copy of the database. ... However you can toggle the shiftkey bypass from another mdb file. ... When you want to implement security, you create a new mdw file, ...
    (microsoft.public.access.security)
  • Re: MDB remembers old MDW
    ... There were 2 reasons that I thought that the mdb had a link to the mdw: ... Group permissions the old groups from 'Security.mdw' were displayed. ... migrating all of our back-end databases to SQL Server 2005. ...
    (microsoft.public.access.security)
  • Re: MDB remembers old MDW
    ... There were 2 reasons that I thought that the mdb had a link to the mdw: ... When you looked at the Workgroup Administrator dialog it displayed ... Group permissions the old groups from 'Security.mdw' were displayed. ...
    (microsoft.public.access.security)
  • Re: Multiple Databases - One Workgroup
    ... > that one database with each database have different permissions for ... For the two secured mdb files. ... Unsecure those databases by ... Now join your one mdw that you want to secure all databases with. ...
    (microsoft.public.access.security)