G
Guest
Hi Joan,
< It could be that PC1 or PC2 is joined by default to a mdw that isn't a
standard system.mdw (or is one that has been modified)?>
Since the Wizard creates a new mdb with a random SID for Admins, strips
Admin and Users of all permissions, changes the owner from Admin to the
curent user and assigns the new user a random SID, I don’t see how any
modification to system.mdw would allow it to open the secured mdb. Can you?
The only way I can explain what’s happenign is to assume that the Wizard in
this version of Access doesn’t change the Admins SID stored in the mdb file
if it is different than the Admins SID of the system.mdw of the current PC.
Can you think of any other explanation? If I’m right, you would agree that
this is a flaw in Access, or is there a valid reason for this behaviour?
< It could be that PC1 or PC2 is joined by default to a mdw that isn't a
standard system.mdw (or is one that has been modified)?>
Since the Wizard creates a new mdb with a random SID for Admins, strips
Admin and Users of all permissions, changes the owner from Admin to the
curent user and assigns the new user a random SID, I don’t see how any
modification to system.mdw would allow it to open the secured mdb. Can you?
The only way I can explain what’s happenign is to assume that the Wizard in
this version of Access doesn’t change the Admins SID stored in the mdb file
if it is different than the Admins SID of the system.mdw of the current PC.
Can you think of any other explanation? If I’m right, you would agree that
this is a flaw in Access, or is there a valid reason for this behaviour?