A
anovak
A colleague has created numerous sub-plans and for some tasks, there
are inter-project links. All these projects were created as *.mpp
files and from his c: drive.
I walked him through the import wizard for the importing of all the
sub-plans into the server. However, all of the inter-project links
still reference the *.mpp project on the c: drive.
1. What is the easiest way to get all these inter-project links
changed to where they are referencing the version of the project on
the server?
2. I've read about creating inter-project links via deliverables.
However, it seems to me that once the dependencies have been
established....big deal? How is a PM alerted / shown that the task
having the dependency on the deliverable is scheduled to start late if
the deliverable is late in the predecessor project? Perhaps I'm
reading too much into this, but deliverables don't seem to bring that
much value to the table in terms of inter-project dependency tracking.
Please advise.
Thanks,
Andy Novak
UNT
are inter-project links. All these projects were created as *.mpp
files and from his c: drive.
I walked him through the import wizard for the importing of all the
sub-plans into the server. However, all of the inter-project links
still reference the *.mpp project on the c: drive.
1. What is the easiest way to get all these inter-project links
changed to where they are referencing the version of the project on
the server?
2. I've read about creating inter-project links via deliverables.
However, it seems to me that once the dependencies have been
established....big deal? How is a PM alerted / shown that the task
having the dependency on the deliverable is scheduled to start late if
the deliverable is late in the predecessor project? Perhaps I'm
reading too much into this, but deliverables don't seem to bring that
much value to the table in terms of inter-project dependency tracking.
Please advise.
Thanks,
Andy Novak
UNT