PRJ2000: Unexpected Elapsed Month Duration (242628)



The information in this article applies to:

  • Microsoft Project 2000

This article was previously published under Q242628

SYMPTOMS

In Microsoft Project 2000, when you enter duration values in elapsed months (emon), tasks may finish earlier or later than expected depending on whether the project is being scheduled from start or finish.

CAUSE

This behavior occurs because Microsoft Project uses the Days per month setting on the Calendar tab (click Options on the Tools menu) to determine the number of days in a month. For example, when you enter a duration of 1 elapsed month (1 emon) it is the equivalent of entering 20 elapsed days (20 edays), based on the default value of 20 in the Days per month box.

WORKAROUND

To work around this behavior, enter durations using elapsed weeks (eweeks) or elapsed days (edays). If you want Microsoft Project to consider non-working time, use months (mon).

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Duration is the total span of active working time required to complete a task. This is generally the amount of working time from the start to the finish of a task, as defined by the project, the resource calendar, and/or the task calendar.

Elapsed duration is the amount of time it takes to finish a task, based on a 24-hour day and a 7-day week.

Modification Type:MajorLast Reviewed:10/17/2002
Keywords:kbbug KB242628