Securing a Project File

[Michael]

I am looking for a way to secure a project file so that
no one can make changes to it. I have set it up to
include a password for editing, but my problem is that if
the end user saves the file under a different file name,
makes changes, then saves it back to the original file
name, I have no way of tracking those changes. Any
suggestions?

 

[Paulo Calvário]

Did you try with PFD Writer?
You will lose the Project facilities, but the data remains ...
This is not a good solution, but only an idea ...

Paulo

 

[Rob Schneider]

What you want to do can't be managed by Project directly. Recommend:

1. when you "publish" the schedule for communication purposes, write a
document and elaborate on the plan, include screen shots (via camera
icon), paste in tables, etc. Don't count on users having to have Project.

2. ok to release the project file, as you do now ... but consider
putting protection on the file system to stop the ability for people to
write back to the original file. Use permissions on the computer for
file server. You retain all read/write permissions, but others who you
don't want to write only have "read" permissions.

Hope this is useful to you. Let us know.

rms