Unique ID Successors

[AMH]

Hi,

Looking for some help, with project 2003. This seems quite complex so will
describe the best I can

I have a series of projects that are inserted into a programme plan, there
are dependencies between projects which are dynamically linked within msp.

In order to produce status reports for management I export data into excel,
however I have found a problem with respect to predecessors and successors,
and here goes :

Example
Individual Project Plan level (all seems to be fine here)
Dependency within Project Plan has
Unique id of 76
Has a successor of task 119
Successor task Unique ID 44
Therefore in column successor Unique ID 44 is shown
Task at line 119 has a unique ID of 44
All is fine


However when the above project is inserted into the programme level plan,
the following occurs
Dependency within Project Plan has
Unique id of 348127308
Has a successor of task 119
Successor task Unique ID 44
Therefore in column successor Unique ID 44 is shown
However the Unique ID of the successor (line 119 of the original project
plan) is now 348127276

So to summarise the unique ID of the successor in the programme level plan
is actually the unique id of the successor in the project level plan and thus
I cannot trace the relationship between the two (I cant use the line id as
all the inserted project will have a line id of 119)

Any ideas ?

 

[Jack Dahlgren]

You can add a text field and put whatever unique values you need to produce
reports.
I'd also consider doing a custom export to excel using VBA. What exactly are
you trying to export and why?

-Jack Dahlgren

 

[AMH]

With all the inserted projects I've got a programme plan of around 10,000
lines so I don’t really want to be add text fields to each dependency
predessor/successor.

I already produce an excel report that reports on programme and project
milestones and provide a history, week on week, to give management and idea
of trends within the programme and individual project. They like this report
so much that they would like it expanded to cover dependencies, and thus I am
trying to identify within extract from the programme plan dependencies
between projects and from external sources.

All dependencies are identified using a flag, however the predecessors or
successors are not, thus I am trying to identify them. This would be simple
if the unique id in the programme plan successor column identified the unique
id in the programme plan rather than the unique id at the project level


I am tryign

 

[Jack Dahlgren]

Dependencies are not easily identifiable in Project (I've written many times
that they should have a complete set of properties just like tasks do) so I'd
work this a different way. You can continue to link from project to project,
but instead of linking to a task, link from a dependency milestone in one
project to a corresponding milestone in the other project. They can be coded
or tagged so that you can easily find them.

Project 2007 takes this approach and has a new feature called dependencies
which are exactly this sort of thing.

You don't need to flag all 10000 tasks. Just tag the ones which are
interesting to you. I'd be surprised if management needs trends on all 10000
tasks.

-Jack Dahlgren