Y
Y Lee
We use a 6.5 hour day in Project (Pro Server 2002), scheduled from 9:00 AM to
3:30 PM. We have published a plan to have resources enter vacation time as
new tasks using the “Create New Task†function on the Web Access.
Here is the problem. It seems as though the server interprets everything in
5 hour days. If I submit a test task for 2d duration ( which should
represent 13 hours), it comes over as 10 hours and schedules across a day and
a half. If I submit 6.5 h as the duration, it comes over as 6.5 hours and
schedules properly. No manner of tweaking the project or resource calendars
makes a difference.
Both the Project Calendar and Resource Calendars are set to 6.5h Days and
32.5 hour weeks. The default task Type is set for “Fixed Workâ€.
And to head off the obvious reply: management is adamant about having
resources enter the duration in terms of days.
3:30 PM. We have published a plan to have resources enter vacation time as
new tasks using the “Create New Task†function on the Web Access.
Here is the problem. It seems as though the server interprets everything in
5 hour days. If I submit a test task for 2d duration ( which should
represent 13 hours), it comes over as 10 hours and schedules across a day and
a half. If I submit 6.5 h as the duration, it comes over as 6.5 hours and
schedules properly. No manner of tweaking the project or resource calendars
makes a difference.
Both the Project Calendar and Resource Calendars are set to 6.5h Days and
32.5 hour weeks. The default task Type is set for “Fixed Workâ€.
And to head off the obvious reply: management is adamant about having
resources enter the duration in terms of days.