Prev: why is the options option greyed out?
Next: Keep hyperlinks afer save as html
From: AnthemAZ on 21 Jan 2010 16:31
My company has many programs with very large files. I have recommended
breaking these files into smaller subfiles and inserting each of these sub
files into a master so they can be accessed by more than one person. Server
in on the horizon but not available yet.

When this is done, the difficult area is to re-link the tasks now between
sub projects that were originally linked together while in the one file.

Do anyone have a macro, checklist, process, that can help expedite this and
check to ensure the subproject are relinked to the same task as they were
before the split?

As you know, when working over a network, the predecessor and successor
fields become very long due to the notation of
K:\folder\subfolder\subsubfolder\etc.......
This makes it very difficult to check.

Any advise will be appreciated.

Thanks,

AnthemAZ




From: John on 21 Jan 2010 21:50
In article <41D13EBB-EF41-4ABD-BC61-5D4AD158FD71(a)microsoft.com>,
AnthemAZ <AnthemAZ(a)discussions.microsoft.com> wrote:

> My company has many programs with very large files. I have recommended
> breaking these files into smaller subfiles and inserting each of these sub
> files into a master so they can be accessed by more than one person. Server
> in on the horizon but not available yet.
>
> When this is done, the difficult area is to re-link the tasks now between
> sub projects that were originally linked together while in the one file.
>
> Do anyone have a macro, checklist, process, that can help expedite this and
> check to ensure the subproject are relinked to the same task as they were
> before the split?
>
> As you know, when working over a network, the predecessor and successor
> fields become very long due to the notation of
> K:\folder\subfolder\subsubfolder\etc.......
> This makes it very difficult to check.
>
> Any advise will be appreciated.
>
> Thanks,
>
> AnthemAZ

AnthemAZ,
I do have a macro that will do the second part, convert a dynamic master
into a static master while maintaining the links, but I don't have a
macro that will create a dynamically linked set of subprojects from a
static file. The latter of course could be developed.

As far as the best approach to use, it depends on how many files are
involved and how many cross project links would be needed in a dynamic
configuration. Personally I'd develop the VBA code to automate the
process, especially since you mentioned you need to do this on multiple
large static files. Then I'd use my existing macro to reverse the
process for back-check. Of course there's still the issue of comparing
the original large file with the new back-converted file. Unfortunately
the Compare Projects utility won't help since it works based on the
Unique ID and both files must be of the same heritage.

If the number of cross-project links needed after the breakup is not
large, say less than 25, you might just want to bite the bullet and do a
manual conversion. You can use spare text fields for reference
source/destination data to help facilitate the manual process - exactly
what I would do if I were developing a macro to do the "file breakup"
conversion.

John
Project MVP
 | 
Pages: 1
Prev: why is the options option greyed out?
Next: Keep hyperlinks afer save as html