As soon as a predecessor task comes out of a none work period the successor task will drop into the first available work day available in its own calendar.
A milestone - having no duration - will drop into a very small gap - even 1 second long.
So make sure you calendars and work patterns are concurrent with no gaps.
Also check what calendars are on the resources.
Best regards
Mike Testro.
Member for
16 years 7 months
Member for16 years7 months
Submitted by Gary Whitehead on Thu, 2011-07-07 08:50
I don't have 2007 so not 100% sure, but could this be because a milestone has zero duration, and hence there is no work being done on the milestone during the non-work day of 30/12/11?
What happens if you make the milestone a 1 day activity with a -1d lag?
Member for
19 years 10 monthsHi Stuart As soon as
Hi Stuart
As soon as a predecessor task comes out of a none work period the successor task will drop into the first available work day available in its own calendar.
A milestone - having no duration - will drop into a very small gap - even 1 second long.
So make sure you calendars and work patterns are concurrent with no gaps.
Also check what calendars are on the resources.
Best regards
Mike Testro.
Member for
16 years 7 monthsHi Stuart, I don't have
Hi Stuart,
I don't have 2007 so not 100% sure, but could this be because a milestone has zero duration, and hence there is no work being done on the milestone during the non-work day of 30/12/11?
What happens if you make the milestone a 1 day activity with a -1d lag?