T
TKeire
Hi
I am using Project 2003. I have a project with multiple resources. I have
a standard calendar and then individual resource calendars to reflect any
variances from the standard calendar for the different resources.
My standard calendar shows Sunday and Monday 25/26 June as Non working days.
For resource "A" I have changed these dates to "working". For resource "A"
if I schedule a task to start on the 22/06 with 11d dur it works fine and
allows work through the 25/06 and 26/06. It does not appear to work for the
following scenario:
Task 1, Resource "A" starts on 22/06/06
Task 2 is scheduled "SS & 11d lag" to Task 1, also Resource "A".
For some reason it is jumping the 25/06 and 26/06 even though these are
programmed as working days for Resource "A", thus my 11d lag is really a 13d
lag.
I have played around with this for quiet awhile and can't seem to find any
sensible soln, apart from changing the lag to 9d which is really tricking the
computer. Of course this also leads to the scenario that this problem may be
occurring in other areas that I have not noticed yet!
Ideas/suggestions please?
Tony
I am using Project 2003. I have a project with multiple resources. I have
a standard calendar and then individual resource calendars to reflect any
variances from the standard calendar for the different resources.
My standard calendar shows Sunday and Monday 25/26 June as Non working days.
For resource "A" I have changed these dates to "working". For resource "A"
if I schedule a task to start on the 22/06 with 11d dur it works fine and
allows work through the 25/06 and 26/06. It does not appear to work for the
following scenario:
Task 1, Resource "A" starts on 22/06/06
Task 2 is scheduled "SS & 11d lag" to Task 1, also Resource "A".
For some reason it is jumping the 25/06 and 26/06 even though these are
programmed as working days for Resource "A", thus my 11d lag is really a 13d
lag.
I have played around with this for quiet awhile and can't seem to find any
sensible soln, apart from changing the lag to 9d which is really tricking the
computer. Of course this also leads to the scenario that this problem may be
occurring in other areas that I have not noticed yet!
Ideas/suggestions please?
Tony