Identifying linked-to Ghost tasks

[Martin Wilkinson]

Does anyone know if there is any way to identify just linked-to"ghost" tasks
in MSP2000?

Is there a Filter (or a field I can use to filter)?

Thanks

Martin

 

[JulieS]

Hi Martin,

After some *quick* testing, I believe the following formula will work in a
Flag field:

IIf(Instr([Predecessors],"\")<>0,"Yes",IIf(Instr([Successors],"\")<>0,"Yes","No"))

This will display a Yes if the task has either an external Predecessor or
external Successor. You can then filter looking for only Yes in the flag
field.

Hope this helps. Let us know how you get along.

Julie

 

[DonL]

JulieS,

The easier way would be to create a filter that checks the "External" field
for "Yes."


--
Don L.

Hi Martin,

After some *quick* testing, I believe the following formula will work in a
Flag field:

IIf(Instr([Predecessors],"\")<>0,"Yes",IIf(Instr([Successors],"\")<>0,"Yes","No"))

This will display a Yes if the task has either an external Predecessor or
external Successor. You can then filter looking for only Yes in the flag
field.

Hope this helps. Let us know how you get along.

Julie

Does anyone know if there is any way to identify just linked-to"ghost"
tasks
in MSP2000?

Is there a Filter (or a field I can use to filter)?

Thanks

Martin

 

[JulieS]

Hi DonL,

Yes, I thought of that. However, I assumed Martin was looking for a method
of identifying tasks in the current project with external predecessors
and/or external successors, from his comment "linked-to"ghost" tasks". The
[External] field will show "yes" if a specific task is external but will not
flag if the predecessor or successor is external. Of course, it is possible
that my mind is just on a holiday

Julie

 

[Martin Wilkinson]

Hi,
Really appreciate your efforts. I'm sorry if it wasn't clear, but what I was
after was identifying the actual ghost tasks, which Don's post hit on the
head ( I didn't realise the External field existed)!

Anyway, the bit of scripting which Julie provided was also useful, as it has
raised in my consciousness the possibilities of custom fields, so I will more
confident in tackling more sopisticated problems in the future.

Thanks again

Martin

 

[JulieS]

Hi Martin,

You are welcome and thanks for the feedback. Glad to know that between Don
and I you found what you needed.

Julie

 

[DonL]

Hi JulieS,

Thank you for pointing out your assumption - I wasn't thinking along those
lines, and need to keep on my toes too.
--
Don L.

Hi DonL,

Yes, I thought of that. However, I assumed Martin was looking for a method
of identifying tasks in the current project with external predecessors
and/or external successors, from his comment "linked-to"ghost" tasks". The
[External] field will show "yes" if a specific task is external but will not
flag if the predecessor or successor is external. Of course, it is possible
that my mind is just on a holiday

Julie

JulieS,

The easier way would be to create a filter that checks the "External"
field
for "Yes."

 

[JulieS]

Hi Don L.,

That's the great thing about these ngs -- what one of us misses (me in this
case) another one picks up (that would be you). The good news is that
Martin got the answer he was looking for .

Julie