P
PeterH
In some cases when a PM sets the status date for a project to reflect the
date that their resource's time entry has been completed, and then
reschedules uncompleted work to start after that date, the Actual Work
Protected field displays '0' in some furture weeks.
If the PM then tries to re-forecast work to be done by the resource for one
of those (future) weeks, MS Project automatically enters the time into the
Actual Work field as if the work has already been done.
Any suggestions why this is happening and how to avoid it?
date that their resource's time entry has been completed, and then
reschedules uncompleted work to start after that date, the Actual Work
Protected field displays '0' in some furture weeks.
If the PM then tries to re-forecast work to be done by the resource for one
of those (future) weeks, MS Project automatically enters the time into the
Actual Work field as if the work has already been done.
Any suggestions why this is happening and how to avoid it?