What you need to understand is that duration by definition ONLY includes
minutes worked during the hours defined as Working Time Hours by the
calendar controlling the task. For example, if my calendar says the regular
working day is 8am to 5pm and I have a task that starts at 3pm and the
resource continues work after his "official quittin' time" and finishes work
on the task at 8pm, the Actual Duration of that task is 2 hours, NOT 5
hours. This is implicit in the formal definition of duration. The hours
worked between 5pm and 8pm are overtime hours and time spent on overtime is
never included in total duration. If you need to track it in the total
work, you need to update the work values manually in the usage views. As
far as Project is concerned, work performed outside of the working time
calendar simply does not exist unless you explicitly enter it as Actual
Overtime and it is never included in duration calculations. So in actuality
the system IS calculating the correct duration when your work extends past
5pm - the error is in your belief about what you feel it ought to be. You
really can't get what you want because to do so would violate the basic
mathematics of task duration, just like you can never enter a formula into
Excel that adds 2 plus 2 and gives 5 as the result, no matter how badly you
might like it to be true <grin>.
HTH
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs