You're welcome, Tony. Glad you have it sorted. A quick comment -- when using resource pools and sharer files, you have to be very careful about moving/copying/renaming any file in the mix. As you've discovered -- Project doesn't forget.

I also rarely save master project files -- I consolidate read-only when required for reporting -- but don't save or link to the subproject files.



Julie

Julie,

Helpful advice -thankyou.

Ok, so I thought about your suggestion i.e. to not have a master project and now I can see that it is possible to see resouce allocation across all projects from within a single project (as in my case they share the same resource pool).

So the exam question is what key benefits does the master project approach give you over the separate project approach ?

I hope that this will help others in a similar situation.

Thanks

Tony

I think there is good information to be gained out of master projects and I do use them, I just rarely save them -- rather I create a consolidated project as needed.

The advantages of a consolidate or master project is the ability to present all tasks and see any places where the tasks in different projects may need to feed each other (external predecessors and successors).