Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem with MSP task durations against end dates

Status
Not open for further replies.

tomstox

Civil/Environmental
Jan 18, 2008
1
GI
Good morning, I'm quite new to MSP and require a degree of help. i'm sure this will be an easily resolved problem for someone with a bit of experience, but I'm stuck!!

I've entered a task's duration as 24 months (I've also tried 730 days with the same effect) and the automatically produced end date is exactly 2 months short of 2 years from the start date. i think i've set up my working hours / days etc correctly so i'm not sure what the issue is.

any help would be appreciated.

Regards

Tom
 
Replies continue below

Recommended for you

when u specify 730d from for example 2008/Feb 22, MSP will put the end date in 2010/Dec 09, because it is assuming that u don't work at weekends, so you lose 2 days per week.
If you specify 24mon, the end date (in my case) is 2009/Dec 24, because in the Tools->Options->Calendar my MSP defines 1 mon = 20 working days;
Now, if you realy need 2 years -- 2 exact years -- you can specify it as 730ed = elapsed days;
Elapsed time is used for tasks that take that duration independently of the number of resources assigned and if there is someone working on it or not -- for example, if u need to wait 48 hours for some concrete structure to dry, that will take always 48 h, no mater if u ave or not someone present, no mater if it is a weekday or weekend; in this case, your task time is not 48hr but 48ehr

Beste regards
jmn
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top