Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/172905

From BetaArchive Wiki
Knowledge Base


Article ID: 172905

Article Last Modified on 1/20/2007



APPLIES TO

  • Microsoft Project 98 Standard Edition



This article was previously published under Q172905

SYMPTOMS

In Microsoft Project 98, if you copy resource assignment information and paste this information to another task multiple times, the work for all resources will be recalculated incorrectly.

CAUSE

This problem occurs because Microsoft Project interprets the level of effort contributed by this resource as increasing each time the resource is reassigned.

STATUS

Microsoft has confirmed this to be a problem in the versions of Microsoft Project listed above.

MORE INFORMATION

Each time the resource is copied to the task, the work will be recalculated as though the level of effort for the resource has increased. This causes the work for the remaining resources to be redistributed. For example, in task usage view, if you have two tasks ("T1" and "T2"), which are both 1 day (1d) duration, and assign two resources (R1 and R2) to T1 and one resource (R1) to T2, the distribution of work will look similar to the following in task usage view:

   T1
      R1  8hrs work
      R2  8hrs work
   T2
      R1  8hrs work
                

When you copy the resource assignment for T1 and then select T2, the distribution will look like this:

   T1
      R1  8hrs work
      R2  8hrs work
   T2
      R1  8hrs work
      R2  8hrs work
                

When you paste the resource assignment, the distribution will look like this:

   T1
      R1  8hrs work
      R2  8hrs work
   T2
      R1  4hrs
      R2  4hrs
                

And, if you paste the assignment again, the distribution will look like this:

   T1
      R1  8hrs work
      R2  8hrs work
   T2
      R1  2.67hrs
      R2  5.33hrs
                

The resource R2 is now overallocated but this is not evident and you receive no warning while using task usage view. To see the overallocation, switch to resource usage view.

Keywords: kbbug kbpending KB172905