Locking down fields

[Randy]

I'm wondering if there is a way to lock down a custom field so that a PM
cannot change the value. We are running MSP 2003 Server environment.

Thanks!

Randy

 

[Dale Howard [MVP]]

Randy --

No, sorry. When you create a custom enterprise Project field or outline
code, or a custom enterprise Task field or outline code, you cannot prevent
your PM's from setting/changing the values in those fields or outline codes.
Therefore, I would recommend you handle this as a training and performance
issue. Hope this helps.

 

[Reader Rabbit]

I don't know about the interaction of the PWA with enterprise fields as far
as being able to enter data, it would probably require a hell of a lot of
code and not be worth it, but yes you can make project 2k3 pro fields read
only.

We have had to do this in some of our projects for certain fields that are
brought over from our accounting system (ie task cost to date and what not).
You would have to make a macro.
Macro's have always been a bit of a misnomer for me.
By my understanding they are simple routines that are automated scripts of
user clicks that exist within the program.
However with vba and .net a macro is a hell of a lot more than that.
We have custom macros that pull data from our accounting server and match
them with the exisitng task in the project and stick data into a custom
field.
Then through the always running macro we just dont allow any other text in
the field.
Now I suppose it's possible to halt the macro then make modifications, but
if a user is giong to go through that much trouble then they are gonna get
you some way some how anyway.

Hope this helps some.

R

 

[Randy]

That's what I figured. Thanks!