System.mdw (WIF)

  • Thread starter Thread starter Linus
  • Start date Start date
L

Linus

I've have extensively searched for answers regarding the setup of a security
file and have finally succeeded in getting it to work as long as I run the
Db's I have developed on my PC.

Basic question is this:

How does the Db which is copied onto a centralized server use the mdw file I
have created, if the mdw file does not transport with the Db? Does every PC
user have to have this particular mdw file installed on their own PC for this
to work?

Thanks,

Linus
 
Thank you for your clearly stated answer.

Does MS have any plans to include the security file with the Db to eliminate
this problem?
 
Ok, thank, Chris for your assistance.
--
Linus


Chris O'C via AccessMonster.com said:
Sorry, it's part of the design to enable (or enforce) security whenever a Jet
db file is opened. The user is joined to the designated mdw file (workgroup)
before opening the db file. The user and group membership is checked in the
mdw file and then compared to the authorizations in the db file for that user
and the groups the user belongs to. If the user isn't a member of that
workgroup or doesn't have permission to open the db, the db file doesn't open.


Thus the mdw file and the secured db file have to be separate files because
the security file (mdw) has to be opened first to determine if the db file is
allowed to be opened. You can put the mdw file in the same folder with the
back end db file if you want to keep them together.

Chris
Microsoft MVP
Click to expand...
 
Back
Top