I think that if you check you will discover that even if the "scheduling
ignores resource calendar" option is not selected that a resources base
calendar will be over-ruled if a task calendar with a different working
pattern is assigned to the task. If you don't select the option you get a
conflict warning that there is a conflict between the resource and task
calendars and that the task scheduling will ignore the resources calendar.
You will then also get 2 icons in the indicator column, one indicates that a
task calendar is applied the other that there is a conflict with
insufficient "Intersecting" calendars.
If you apply a task calendar and select the "scheduling ignores resource
calendar" the only difference is that you get no warning sign.
The existence of task calendars allows "normal rules" to be suspended in
specific circumstances to model an exception. By default all tasks are
scheduled on the base calendar for the project consequently the task
calendar option shows blank (what is the point of stating the obvious?),
resources can influence the scheduling of tasks by virtue of the concept of
Resource Driven Scheduling - in the main I always reccomend that an
organisation creates a company base calendar that is then employed in all
projects AND the Resource Pool to ensure projects and resources are in synch
(this is very elegantly supported by the Enterprise options available with
Project Pro & Server), any task calendars then assume precedence in terms of
scheduling.
--
Dominic Moss
www.projectability.co.uk
Helping people achieve more with Microsoft Project
Tel +44 8707 303 400
Fax +44 8707 303 500