Consolidated Links/External Links

[Brian]

Does anyone know of any VBA Code written that would allow one to take
multiple project Files, map them into one file and then map the External

Links which were part of the original source files and establish the
pred/successor relationship within the new integrated master file?

The idea is to create a single IMS out of multiple consolidated files
but preserve the hyperlinks (giver/receiver relationships).

 

[John]

Brian,
No need to double post. Those of us who answer check all appropriate
newsgroups. See my response in the .project newsgroup.

John

 

[Microsoft]

I am working on a similar problem. Thus far we have listed the default
project files to be consolidated in a user file, allowing users to update
the file names if required (they sometimes append dates or version numbers).
We then just use ConsolidateProjects once the user clicks a command button.
Very simple, although there are limits to the ConsolidateProjects method.
There a just a few lines of code, eg, appending paths and file names, which
are taken from the user form. I just used a macro to obtain the
ConsolidateProjects method. The rest was trivial - not much code apart from
my user form.

We are still working on the dependencies, but we have adopted a convention
that "inputs" and "outputs" for each plan are made milestones and we then
use Flag1 or Flag2 to indicate if the milestone is "normal" or an
input/output to be mapped in this second stage. I expect this to be more
complicated!

However, MY problem, if anyone can help, is finding a way to access the
FileOpen or any other dialog just to retrieve a file path for the project
files, WITHOUT opening an actual file. Is there any way to subclass a
method or to incorporate such a dialog without actually opening one of the
files? I use a default file path but need to give the user the chance to
look elsewhere as well.

Does anyone know of any VBA Code written that would allow one to take
multiple project Files, map them into one file and then map the External

Links which were part of the original source files and establish the

 

[John Flynn]

Minor typos - (1) I meant user form, not user file (although we are also
adding an "INI" file equivalent to store text between sessions) and (2)
horrified to be labelled Microsoft, even in a MS newsgroup. Forgot to
change newsreader settings!

Thus far we have listed the default project files to be consolidated in a

user file, allowing users to update

the file names if required (they sometimes append dates or version

numbers).