Re: 4x10 calendar problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Take a look at the FAQs entry on Default Working Hours at the URL in my signature.

Durations are always stored in hours (well, minutes to get technical). The entry on the Tools Options Calendar page labels "Hours per Day" is the conversion factor that Project uses to convert a entry typed in in "days" into the required hours to store in the database. So if your working time calendar has hours of work 7am to 6pm MTWT with an hour for lunch but you have left the "hours per day" at the default 8 and you enter a task with a duration of "4 days," that task duration is converted to 4x8 or 32 hours. Then starting Monday at 7am, Monday at 6 is 10 hours, Tuesday at 6 is another 10, Wednesday at 6 is another 10 - that's now 30 so far leaving 2 still to go - and so the task will finish Thursday at 7am+2 or 9am. Another 4-day task linked as a successor to that one will then be able to start and so it will show a start of 9am Thursday and will finish 32 working time hours later or the following Wednesday at 11am. And so forth throughout your project.

The default start and ends times on the calendar options page don't affect any of this - in fact, they don't affect the calendars at all. All date fields in Project are really date/time fields. If you manualy enter a date and don't type the time, depending on whether you are entering a start time or finish time field Project uses the entry in the default start or default end field to supply the time it assumes you mean.
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs



"Hadi" <Hadi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:ED05B420-31C0-479D-B0A0-C370B9EDB1DD@xxxxxxxxxxxxxxxx
Hi,

I have a problem with a custom calendar I created. I went to tools-->change
working time and created a 4x10 calendar with MTWTH as 10 hr working days. I
also went to tools-->options-->calendar and changed the figures there to
match that. The new working day is from 7Am to 6PMM with an hour lunch.
everthing seems OK so far. After I created nearly 20000 tasks i found out
that alot of the tasks dont start and finish like i told it. for example,
lets say I have task1 @ a 4 day duration. I thought the taks would start
monday @ 7AM and finish on Thursday @ 6PM but whaat i found out is the some
of the tasks start @ 7Am and finish at @2PM or 3PM not 6. so alot of my
resource hours are screwed up since I used units when i assigned resrouces to
these tasks and not hours. I am not sure why it did that?? any thoughts of
how the problem originated and how to fix it


many thanks

.



Relevant Pages

  • Re: Actual Work moving to future
    ... duration hours have elapsed and vice versa, ... >> What that setting will do is when you post progress it disconnects task ... >> shows a day shift, ...
    (microsoft.public.project)
  • Re: Actual Work moving to future
    ... duration hours have elapsed and vice versa, ... >> What that setting will do is when you post progress it disconnects task ... >> shows a day shift, ...
    (microsoft.public.project)
  • Re: Problem with dates/durations on a plan containing imported dat
    ... duration, that you expect your resources will require to complete the work. ... and the resource assignment but NO dates at all (other than the single entry ... >> and I look at a task that says we must produce 80 fids. ... >>>> Project Calendar to see what the master hours of work are? ...
    (microsoft.public.project)
  • Re: Multiple Work Calendars and Duration
    ... The base unit of duration is the minute. ... according to the conversion factor on the Tools Options Calendar ... will take one person 24 hours to do so you're putting 1 day shift, ... Use the split screen to assign the resources. ...
    (microsoft.public.project)
  • Re: Calendar duration
    ... resource brought in who charges an hourly rate with a minimum - say, ... I'll try to explain why I actually need the elapsed time. ... cost per month no matter what the actual calendar states. ... >variable to get the duration. ...
    (microsoft.public.project)