A
aclaar877
I am having a problem with MSProject moving task end dates way out int
the future, even though I haven't changed duration, nor have I resourc
leveled the task. For example, an 80-hour task, fixed work, 75
complete, with resources working full time ends up with an end dat
getting kicked out several months. It's not a predecessor problem.
This usually happens when I've updated resource loading or pasted a tas
into the project from another project. Regardless, the end date make
no sense. Any advice as to what is going on here
the future, even though I haven't changed duration, nor have I resourc
leveled the task. For example, an 80-hour task, fixed work, 75
complete, with resources working full time ends up with an end dat
getting kicked out several months. It's not a predecessor problem.
This usually happens when I've updated resource loading or pasted a tas
into the project from another project. Regardless, the end date make
no sense. Any advice as to what is going on here