Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Problems by linking between Project?

2 replies [Last post]
Daniel Højer
User offline. Last seen 7 years 30 weeks ago. Offline
Joined: 15 Feb 2007
Posts: 13

Normally I work with Primavera, but is currently working in a organisation where they are using MS Project.

I have suggested that we link activites in different projects (files), as one development project is split into several areas each having thire own plan.

The other planners in the organisation then told me, that it is not possible due to performance. One of the statements is: "Generally when hard link is used while opening the plan or saving or publishing the master project will try to refresh the child projects with the updated data hence there is a performance issue in this type of linking. More over if the links are with big project the issue becomes more."

and

"while linking projects we are handling a lot of data ( all the tasks and their fields and their values). So it is a bit natural to face a performance issue for sub projects  but if we can have more faster network or servers or if we only link small projects to link that can reduce the issue."

 

Is it correct that MS Project cannot handle links between projects (we have between 30 and 600 activities per project)?

If it is correct how can we then see the dependencies between plans and the consequenses of an delay in one plan?

Replies

Mike Fenton
User offline. Last seen 8 years 1 week ago. Offline
Joined: 25 Apr 2011
Posts: 10
Groups: None

When linking projects the way you propose, the stability of the network becomes important. There is an increased risk of files becoming corrupted when saving linked projects. Most people open their projects from the server and save to the server. Each time you do this there is a risk that the server transmission could be interupted. This usually isn't an issue with properly supported networks.

The other issue would be if you have multi-users trying to access the same files. In an environment where you have several planners trying to modify the one file, this could cause some disruption.

The performance issues you mention are related to the sever speed. Generally though most modern networks are capable of opening multiple projects with links within a few seconds.

mike