Use relative path name for linked projects?

[michael.franke]

Hi again

I've split my large project into half a dozen smaller ones, and there
are a few dependencies between them. Is there any way to make sure
that these links between projects use a relative path name, rather
than an absolute one? Not only is the absolute path name really
cumbersome, it's dangerous, as I'd like to be able to copy the entire
directory of sub-projects and have them all still point to one
another!

Mike

 

[JulieS]

Hi Mike,

Sorry, no. The links all use UNC. The recommendation is to put all
project files you intend to link in one directory then you can copy
the folder as needed without spending time re-linking.

I hope this helps. Let us know how you get along.

Julie
Project MVP

Visit http://project.mvps.org/ for the FAQs and additional
information about Microsoft Project

 

[michael.franke]

OK, hold on. I just moved and renamed the folder, and opened up my
"Master" project again, and it seems to be correctly linking to
predecessors in projects that are in the right place (the place I just
moved the project to). So I guess MS Project does use relative
pathnames. Or at least it looks for the subprojects and links when it
opens up.

Am I understanding this correctly?

Mike

 

[JulieS]

Hi Mike,

If the project files are in the same folder they will update
correctly. If they are in different folders no. You are only
seeing the "short version" of the UNC because they are in the same
folder.

I hope this helps. Let us know how you get along.

Julie
Project MVP

Visit http://project.mvps.org/ for the FAQs and additional
information about Microsoft Project

 

[Andy Marden]

Having trouble with MS Project 2003 in exactly this area. I've always been able to keep master and sub-project together (together with resource pool) in the same folder and it all waorks when you move things around. owever, at this client, things are different. I've done some tests and have discovered that when things are saved ina folder on a local drive (or anything starting with a drive letter) it work fine.

However, if this is moved on a network drive, everything becomes absolute - lins to sub-projects, reosurce pool and it can only be refactored manually which is horrible (especially the resource pool).

It seems tht project is using something to interpret file paths which returns a \\ UNC for network drives but is then unable to work out what that means form a relative path perspective. It could just as easily use drive letters but choooes not to.

Aside from fuming about the amount of grief this has given me and he fact that this is really poor programming, I'm looking to find a way round it and alsop to understand if it is fixed in later volumes of Project.

The only thing I can think of (save upgrading or using Project Server) is to introduce a readonly version control system to save the projects in on teh network and then people check them in and out locally to their PC and work on them that way.

I wonder if it also a factor in the way the network is configured here or works this way for everyone.