A project normally has exactly one critical path. That path belongs to the
project as a whole, not to any one area of the project plan. The definition
of a critical path is that path taking the longest time through the network
representing the minimum completion time for the project. So, you really
cannot analyze only one portion of the project in hopes to see a different
path because it does not exist.
The management literature defines the Critical Path as those activities with
no more than 0 days of total slack. Although there is no filter in Project
that will allow you to selectively ignore certain tasks, Project will allow
you to change the definition of a critical task.
You can go to Tools/Options... pull the Calculations tab. At the very
bottom you can select a non-negative integer value for the number of days
slack to define a critical task. In doing so, *all* activities with less
than this amount of slack will be considered critical.
Your problem is that you want to exclude a task that already has 0 days
slack so Project is not going to be able to help you directly. I you really
want to analyze a section of your schedule, you would have to copy out that
section into a new project file without all the other tasks and do a critical
path on just that. Keep in mind that this analysis is *not* applicable to
the overall project schedule.
--
If this post was helpful, please consider rating it.
Jim
It''s software; it''s not allowed to win.
Visit
http://project.mvps.org/ for FAQs and more information
about Microsoft Project