Cindy said:
Sorry to sound so naive. However, the supervisor who is in charge of the
master project file does not want the burden of entering passwords in order
to open the master file.
Cindy,
Reading between your lines I get the understanding that individual users
have incorporated password protection into their files. Then when the
supervisor, who only looks at the consolidated master, tries to open the
master, he/she is queried for the passwords of each subproject. Correct?
Unfortunately there is no way around that. As long as the master is a
dynamically consolidated file (i.e. dynamically linked to each
subproject), then whoever opens the master will need the password of
each subproject, otherwise what would be the point of password
protection if a simple consolidation could defeat it?
Is there a real good reason each user needs to password protect his/her
file? If the answer is "yes", then about the only method I can see
around it is if the supervisor has someone else build a static master
(i.e. subprojects not linked to the master) each time the supervisor
needs to view the information. That designee would of course have to
input each password to create the static master.
On the other hand, if you really don't have a good solid reason for
password protection (sometimes people just want to feel safer from
probing eyes), then eliminate the password protection. If the issue is a
fear that some unauthorized person is going to "mess" with a user's
file, the best approach is a good dose of training and "rules of
engagement". That won't stop inadvertent changes or the deeds of a
never-do-well, but there are ways to detect changes to a file.
Hope this helps.
John
Project MVP
