It does calculate the critical path, if I was to delete the inactive tasks. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 7. Report abuse.
Details required :. Cancel Submit. Trevor Rabey. Rather than de-activating the tasks, just set their durations to zero. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. In reply to HarshDev's post on January 16, Yes, but does it then show the critical path?
In reply to Trevor Rabey's post on January 16, Don't know. I don't want to zero out duration of a few hundred lines and then put them back in. I could make a duplicate file and play with it. A subscription to make the most of your time. Try one month free.
This site in other languages x. Any ideas? I have to assign that calendar to task 47 because that task is based on calendar days and not working days. By the way, the bars for the tasks after task 47 are correctly highlighted in red as critical tasks. I took a brief look at your screen shots and it's not real clear about what is not showing on the critical path. For task 47 I see what appears to be two Gantt bars, one of which far right side of screen shot is red, indicating critical path.
The only task in the sequence shown that doesn't appear as critical is task ID 39 but the main bit of information that is lacking is the Total Slack field. That field will clearly show which tasks are critical. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback.
In essence, my problem is with the first Gantt chart of my post. The second Gantt chart is fine because the critical path is clearly highlighted in red, but not the first Gantt chart.
The only change I made as I indicated in my post, was to change the calendar for task ID 47 for the critical path to be highlighted as can be seen in the second Gantt chart.
That is where I have a problem, as to why isn't the critical path highlighted in red on the first Gantt chart, just because of the different calendar assigned to task ID Okay, but again, you need to look at the Total Slack field. Then we'll have a starting point for an explanation. It is the calendars that is putting a gap in the CP.
Then you will see the small gap. If you switch to the schedule table, you will see the task which has a little bit of total slack which corresponds to the calendar gap.
If you go to file, options, advanced, you can change to definition of critical to, say, 1 day instead of 0 days, and this will then include your tasks which have a bit of total slack in the critical path.
A close look indicates that the Defects Period task has 2 days of Total Slack. The weekend between the end of that task and the start of its successor is working time for the predecessor but not for the successor. So the "Critical" threshold needs to be bumped to 2 days to capture that task. Of course such an approach brings the risk of false positives in a complex schedule - which this one obviously isn't. Much appreciate it. Bumping the Defects Period by the two days fixed the problem.
See attachment. The only problem, slight one, is that the programme no longer reflects the correct Defects Date. You seem to be trying to achieve objectives which are mutually exclusive, ie you can have durations or dates or a continuous critical path, but not all of them.
Or maybe you can if you do what I said earlier and bump up the definition of critical until it includes all of your tasks.
