PC Requires Password

[Guest]

I have a user who created an Access database with table-level security
settings. User B created the database and all of the security settings while
logged in on User A's computer, under User B's Active Directory account. The
security settings within the database are tied to each user's Active
Directory account. Now, for some reason, when User A logs into his own
computer and tries to access the database, it asks him for User B's password.
When User A tries to access the database from any other computer, it works
fine and does not request any password. It's only when User A tries to
access the database from his own computer that he is asked for a password.

It sounds like the problem has something to do with profiles on the computer
or something like that. I'm not AD savvy enough to point my finger in the
right direction. Can someone provide some possible solutions, as I can't
think of anything offhand?

TIA.

 

[Lynn Trapp]

It simply means that User B created the "security" and User A's computer is
now joined to the secure workgroup file that was used to "secure" the
database. Run the workgroup administrator on User A's computer and join the
system.mdw file that shipped with Access. The fact that User A can open the
database on other computers without being prompted for a user name and
password indicates that User B did not successfully implement the security
anyway.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Guest]

It simply means that User B created the "security" and User A's computer is
now joined to the secure workgroup file that was used to "secure" the
database. Run the workgroup administrator on User A's computer and join the
system.mdw file that shipped with Access. The fact that User A can open the
database on other computers without being prompted for a user name and
password indicates that User B did not successfully implement the security
anyway.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

Excellent! Thank you very much Lynn :]

 

[Lynn Trapp]

you're welcome.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

It simply means that User B created the "security" and User A's computer
is
now joined to the secure workgroup file that was used to "secure" the
database. Run the workgroup administrator on User A's computer and join
the
system.mdw file that shipped with Access. The fact that User A can open
the
database on other computers without being prompted for a user name and
password indicates that User B did not successfully implement the
security
anyway.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

Excellent! Thank you very much Lynn :]