Loading...
Quick Links

Reply To: Inactivating Task causing Critical Path to Malfunciton

Home Forums Discussion Inactivating Task causing Critical Path to Malfunciton Reply To: Inactivating Task causing Critical Path to Malfunciton

#414868
Thomas Boyle
Guest

Zack,
In my opinion, your example is a very good illustration of the logical discrepancies that Microsoft introduced with their “fix” of Inactive Tasks beginning in MSP2013+. When introduced in MSP2010, inactive tasks functioned exactly as I expected, and as Daryl has so clearly described. Unfortunately, users who didn’t care about logical consistency or accurate Total Slack ultimately won the day, and their demands are what drives the current goofy behavior. (MSP seems to insert appropriate phantom relationships between the inactive task’s predecessors and successors at run-time, but there is no evidence that the same phantom relationships are properly implemented as part of a backward pass – the late dates of your framing task are incorrect.) This is one more reason not to trust Total Slack in MSP.
Good luck, tom