thanks.... but just so you know you can edit total cost via project.
or else you wouldnt be able to ever get variances etc i.e. everything would
be your baseline.
I find microsofts decision to say on the one hand you can "add" tasks via
PWA but not change existing tasks values as bizzare.
Then coupled with not being able to restrict users from "adding or deleting"
tasks via MS project a further iritant.
In short there is noway for a project manager to delegate the updating of
values and only values for say costs without giving them total access
basically.
I use MS Project to keep track of budget costs of tasks which (as a property
development) firm we have tons of invoices etc which relate to a task and I
have the choice of either a) to enter these myself which is mundane and not
my specialisation or b) give accounts complete access to the project plan
(when i say complete i mean really the ability to modify my plan
significantly i.e. del\add tasks) which is both a security risk and just
plain dumb.
Am i missing something? Is there a reason for this?
Sorry I just cant explain why MS would allow you to add\del (and restrict)
via PWA but not modify existing values? umm but you can delete the whole
thing?
had my cry, thanks for all who helped
