Your description of Project's behavior is spot on, and what I would expect if the Ignore Resource Calendar flag is I've reviewed both the task base calendar and the resource base calendar, and each shows the appropriate work days and times.Įither this is a secret setting I haven't discovered, or there's a bug in there somewhere.Īs an aside, wouldn't it be a wonderful thing if you could use multiple calendars with resources, simply setting date ranges where different calendars apply? Manually changing a Sunday to a work day on an individual resource calendar, with no other changes, will schedule work on a Sunday, which in my mind shows that the 'Ignore Resource Calendar' setting is still honoring the non-work days in the resource calendar. Rather than drive the task work days by the Task Calendar, what I see is a 'logical or' function where non-work days from both calendars are honored and I get three non-working days (Friday - Sunday) when looking at task start To get the proper work days, my logic says apply the remote calendar as a task calendar to all remote tasks, leave the resource calendars as is, and use the 'Ignore Resource Calendar' option to schedule the task per the remote calendar without regard to In executing the project, resources perform work on the first part of the project based on the local calendar, and the last part of the project travel to be on site where the remote calendar applies. I have an international project where typical work weeks are different - and defined with two base calendars, a local Monday - Friday with 8 hours per day, and a remote calendar with Sunday - Thursday with 8 hours per day.

Microsoft project 2016 release date