Predecessor report

T

TooN

I have a problem with making a report. Ive been trying to make a report from
projects to excel with my predecessors. Some tasks have more than 10 external
predecessors. The problem is that they dont show all the predecessors. I
think after a number of characters it stops. Can anybody help me please?

Thanks
 
J

John

TooN said:
I have a problem with making a report. Ive been trying to make a report from
projects to excel with my predecessors. Some tasks have more than 10 external
predecessors. The problem is that they dont show all the predecessors. I
think after a number of characters it stops. Can anybody help me please?

Thanks

TooN,
I assume you are either copying the Predecessor field or using an export
map. Either way, the text string copied/exported will truncate at 255
characters and since external predecessors contain the complete path,
this character limit is easy to exceed. There are various ways around
this. One is to break the task into two or more identical parallel tasks
placing some of the predecessors on each task. Not very elegant but
fairly easy to do.

A second method is to look at the possibility of shortening the path by
decreasing the number of "drill down" folders where each separate
project resides. However this approach may not be possible depending on
your directory structure.

A third method is to designate a spare text field where you can use a
shorthand designation for the predecessor string and then export the
text field. This is a very viable approach but it does require either a
text manipulation formula or a heavy amount of manual entry.

A fourth approach is to use VBA. This is probably the easiest method to
use but it does of course require a working knowledge of VBA.

Several choices, I hope one works for you.

John
Project MVP
 
T

TooN

Thanks John... perfect explenation!!

Gr

John said:
TooN,
I assume you are either copying the Predecessor field or using an export
map. Either way, the text string copied/exported will truncate at 255
characters and since external predecessors contain the complete path,
this character limit is easy to exceed. There are various ways around
this. One is to break the task into two or more identical parallel tasks
placing some of the predecessors on each task. Not very elegant but
fairly easy to do.

A second method is to look at the possibility of shortening the path by
decreasing the number of "drill down" folders where each separate
project resides. However this approach may not be possible depending on
your directory structure.

A third method is to designate a spare text field where you can use a
shorthand designation for the predecessor string and then export the
text field. This is a very viable approach but it does require either a
text manipulation formula or a heavy amount of manual entry.

A fourth approach is to use VBA. This is probably the easiest method to
use but it does of course require a working knowledge of VBA.

Several choices, I hope one works for you.

John
Project MVP
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top