Forum Discussion
Gantt chart help with late, but active task formatting
I have a master project file, where I have several sub projects linked in and I'm having multiple issues, but one thing at a time. First up, I have Baseline Start and Baseline finish set up to ca...
Ok, I can look into changing the scheduling to see what effect that has. Thanks for the explanation.
Calculation was already on...
All the project files live on a shared network drive. The master sits at the root of the parent folder. The sub projects all live one step down in a child folder for that project with all project related materials.
I'm open to other ideas on how to configure this. I'm brand new to Project and am pretty overwhelmed at the moment.
Freeboro,
Your screen shot shows calculation set to "on". Is that before or after I told you that was the issue with your formula (i.e. is the formula now working)?
As I noted, ideally all files in a linked structure should be in a single directory on a local drive. The problem with a remote drive is network glitches. If your network is very stable then it should work okay and as long as nobody moves the files to different folders, the parent/child structure should be okay.
I assume you have a dynamic master which is the default when you create a master with inserted subprojects. However, if all you need is periodic updates of subproject tasks to dovetail with your master, you might be better off with a static master. A static master is simply a snapshot in time of all the files, there is no linked structure and hence the possibility of corruption is essentially null. However, a static master needs to be rebuilt anytime an update is desired but this can easily be accomplish by recording a macro of the first time you set it up. As long as none of the file are moved (i.e. path), just run the macro and you've got an update. To create a static master un-check the "link to project" option just below the selection list in the Insert Project window.
John
Your screen shot shows calculation set to "on". Is that before or after I told you that was the issue with your formula (i.e. is the formula now working)?
As I noted, ideally all files in a linked structure should be in a single directory on a local drive. The problem with a remote drive is network glitches. If your network is very stable then it should work okay and as long as nobody moves the files to different folders, the parent/child structure should be okay.
I assume you have a dynamic master which is the default when you create a master with inserted subprojects. However, if all you need is periodic updates of subproject tasks to dovetail with your master, you might be better off with a static master. A static master is simply a snapshot in time of all the files, there is no linked structure and hence the possibility of corruption is essentially null. However, a static master needs to be rebuilt anytime an update is desired but this can easily be accomplish by recording a macro of the first time you set it up. As long as none of the file are moved (i.e. path), just run the macro and you've got an update. To create a static master un-check the "link to project" option just below the selection list in the Insert Project window.
John
- Ok, I added the calculation to all of the subprojects and that is returning the correct value now, even for the summary rows.
Now back to figuring out the status bars because that isn't working still. - Freeboro,
Sorry, when I suggested the calculation issue I forgot you are working with a dynamic master. The reason the formula doesn't work is because you customized the Flag field at master level. You need to customize it at subproject level. Oh the fun of working with a dynamic structure.
I like your last statement, "to date, none of that has happened". Using a dynamic linked structure in Project is an exercise in probability. As one of our fellow MVPs used to say, "it's not if, but when", when it comes to seeing/feeling the effects of corruption. But, it's not all bad news, linked structures do work but it requires the utmost file management discipline and that can fall apart when multiple users manipulate the files. I think a static master might still be a better option for you but if you still want to stick with the dynamic structure then when a child project is completed, definitely remove it from the master before you archive it.
John - It was already on and the calculation doesn't work, even after closing and re-opening project just to be sure.
Our network is very stable, and until I can prove with very overwhelming evidence that we MUST re-locate the files, this is how it needs to be.
Based on your comment about how to create static masters, mine are dynamic.
The child projects should never move until the project is closed. Then the folder is archived but I can remove the affected subproject from the master at that point. To date, none of that has happened.
