Resource Usage Cumulative Values Change When Scrolling (126106)
The information in this article applies to:
- Microsoft Project for Windows 3.0
- Microsoft Project for Windows 3.0a
- Microsoft Project for Windows 4.0
- Microsoft Project for Windows 95 4.1
- Microsoft Project for the Macintosh 3.0
- Microsoft Project for the Macintosh 4.0
This article was previously published under Q126106
kbusage
SYMPTOMS
When you scroll the timescale in the Resource Usage view, if the view is formatted for cumulative work or cumulative cost, the value in a cell may be changed because of rounding errors that depend on what part of the timescale is visible. For cumulative work, the change can be several
hundredths of an hour. For cumulative cost, the change depends on the
resource rates.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
To compute the cumulative work or cumulative cost for a resource through a
specific date, Microsoft Project gets the assignment work or cost through
that date for each of the resource's assignments, and it then sums the
results. If an assignment finishes before the first visible date on the
timescale, then the exact total work or cost for that assignment is used;
otherwise, a calculation is used that may introduce rounding errors. If you
scroll to the right along the timescale, past the finish date of an assignment responsible for rounding errors, the rounding errors are removed, resulting in different and more accurate values in the cells under
the timescale.
Assignments in which work divided by units gives fractions of minutes
may cause the rounding errors discussed above; although, these rounding errors do not occur in every case. For example, if a resource is assigned 40h of work at .45 units, then Work divided by Units is 40h/.45 = 2400m/.45 = 5333.33m, and, in this case, rounding errors do occur in the calculation of resource usage cumulative values.
Modification Type: | Major | Last Reviewed: | 11/25/2003 |
---|
Keywords: | kbbug KB126106 |
---|
|