Protection

[cheryl]

I am using MS Proj 2002. I have a master project which
incorporates multiple sub projects. I want to ensure that
no one renumbers the WBS, resets the baseline, or enters
hard dates. Does MS Project have a function that allows
me to lock fields?

All comments and suggestions appreciated.

Cheryl

 

[Sean]

Cheryl:

You cannot lock fields within Project Pro. You can try
other circuitous methods to achieve the same effect, but
this isn't worth the effort. Why not password protect
(as long as you're not using server) or save locally.

Hope this helps!

 

[Cheryl]

Sean,
That is the answer I expected. I wanted to be able to
allow mgrs to update without the ability to rebaseline or
renumber the wbs. It is very important that I do this to
keep someone from blowing my schedules up. Too many
reasons to go into here. Any suggestions on a work around?
Cheryl

 

[John]

Cheryl,
As Sean mentioned, it is possible to protect a file from "tampering" but
it requires circuitous methods.

The first and easiest method is to establish spare fields that duplicate
those fields you want to protect. Keep the duplicate fields out of any
views the mgrs will use. A file compare routine can then be used to
compare the protected fields with the duplicate fields to see if any
changes were made. This process is complicated by the fact you are using
a master with subprojects because the "Compare Project Versions" add-in
will not work with consolidated files. You will have to do the
comparison manually or write (or have someone write) a macro that could
do the compare on a consolidated file (it is possible).

The second method, and I have never tried this, is to set up an event
based macro that detects a change to a protected field. If a change is
attempted the change is rejected.

Hope this helps.
John

 

[Cheryl]

Thanks John. I will play with this and see if it will be
useful for me.
Cheryl