Links between multiple projects

Hi Bob,

Might I suggest convincing your client to purchase Primavera?

There are enterprise packages available which would eliminate the problem of loosing your logic links and enable you to successfully manage multiple projects from a single enterprise.

Failing this, good luck with your quest for a solution within MSP.

Regards

Steve

Bob,
unfortunately, MSP builds a file to file link when you want to link two tasks from two separate projects; i.e. you cannot change the name or the folder of either project without losing the link
may I ask why you want to save as projects in this situation?
Alexandre

Alexandre,

Thanks for your response. Each plan has a separate owner and they amend their own plans so I want to restrict each plan to just their relevant content.

Bob

Bob,
1. have each project owner to schedule his own plan and save it as a separate project in his own folder,
2. open a new empty project file of your own, insert these separate projects into your file; be careful to keep each inserted project summarized to only ONE line to avoid that a newly inserted project become part of the preceeeding one,
3. make sure the projects owners do not move or rename their files; the inserted files must be kept at the same place.
Alexandre

Hi all,

Further to what Alexandre suggests


I would open and "save as" using always the same
name and location each and every project.
this way links should not be broken

hth

Bob,

On one of our programmes, we have the same issue.

What I have done is to ensure that the sub-projects always keeps the same file name (e.g. ProjectXXXX_Master.mpp) and is stored in the same location. At issue, it is given an issue and revision reference (e.g. Issue 01 Rev 01) but only within the header or footer, not in the file name.

When the schedule is updated, first of all the user saves a copy of the file as ProjectXXXX_Iss01_Rev01.mpp, which effectively gives an archive copy. The Master file then has it’s header updated to show Issue 01 Rev 02 (or whatever convention is used).

In this way, each issue of the schedule can be identified by it’s unique Issue/Revision reference, whilst the links from the master schedule will always link to the file named ProjectXXXX_Master.mpp.

Hope this is of help.

Tony,

Thanks for that. It pretty much mirrors what I’ve ended up doing so at least I now have some confidence that I’ve got the best (?) solution.

Bob