Dale gave you a way to do this but before you actually put it into
practice step back and re-think whether you really want to or not. If
the project is based on the assumption that every day is a working day,
that means work takes place every day of the week. But a "task" is
usually the activity done by ONE resource or resource team. That
implies that if Joe is assigned to wax widgets, once he starts working
on it he will never take a day off until it's done, even if it takes
several weeks. If that's the work schedule your resources really will
do, fine, go for it. But that would be a very very rare organization
indeed that doesn't give people time off.
Duration normally only includes time that is available for work so that
the relationship between duration time and man-hours of labour holds up.
If you need the know how much "real time" such as your watch tracks or
you see on a wall calendar that a task takes, you should use elapsed
time. There between Mon 8am and Fri 5pm there are 128 elapsed hours but
40 work hours. Since work won't take place unless people are there to
do it, duration the preferable measure to use.
--
Steve House
MS Project MVP
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
Karyn Ryan said:
I would like to set the duration for all tasks of my project (41
dates) to include weekends. I haven't been able to figure out how to
reset the default from 5 work days/wk to 7. If anyone knows how to fix
this I'd love to hear from you! Thank you.