Forum Discussion
Multiple pilots under a single project
When you insert subprojects into a master, you will be able to see all the tasks in the subproject at master level. An engagement task in a subproject will not "start" anything in the master but you could create a link between a subproject task and a task in the master. For example, here is a simple subproject with a start engagement milestone. An external link is created which causes a start in the master. A similar process could be used for a finish milestone.
One easy way to make the external link is to select the desired task in the subproject and then while holding the mouse down drag to the desired task in the master. When the two tasks are widely separated, a quick filter can isolate the desired source (subproject) and destination (master) tasks.
A word of caution however, linked structures in Project (i.e. master/subprojects) are prone to corruption. Adding cross-project links (external predecessors/successors) "ups the ante" for corruption. For reference, with linked structures none of the files should ever be renamed, moved, overwritten or "saved off" to another location. Ideally, all files should reside in a single directory on a local drive and not be operated over a network. Linked structures do not work on SharePoint.
Hope this helps.
John
When you insert subprojects into a master, you will be able to see all the tasks in the subproject at master level. An engagement task in a subproject will not "start" anything in the master but you could create a link between a subproject task and a task in the master. For example, here is a simple subproject with a start engagement milestone. An external link is created which causes a start in the master. A similar process could be used for a finish milestone.
One easy way to make the external link is to select the desired task in the subproject and then while holding the mouse down drag to the desired task in the master. When the two tasks are widely separated, a quick filter can isolate the desired source (subproject) and destination (master) tasks.
A word of caution however, linked structures in Project (i.e. master/subprojects) are prone to corruption. Adding cross-project links (external predecessors/successors) "ups the ante" for corruption. For reference, with linked structures none of the files should ever be renamed, moved, overwritten or "saved off" to another location. Ideally, all files should reside in a single directory on a local drive and not be operated over a network. Linked structures do not work on SharePoint.
Hope this helps.
John
- Thanks. That helps. I may have to reconsider how I've set things up. Thanks again for your help.
- Newtoproject,
You're welcome and thanks for the feedback.
John