Wayne Spray said:
Thanks John! That's what we did in this case. We systematically removed
the links in the 4th project until we found the one that caused it.
I still would like to find a tool which traces through paths in the
schedules and identifies where circular logic exists. That would save time
over the "hunt and peck" method, if this should happen again.
Wayne
Wayne,
I'm glad the "solution" was that simple. I doubt you will find a tool to
ferret out circular relationships other than the algorithm built into
Project itself, (the one behind the error message), simply because a
circular relationship doesn't occur until you attempt to create it,
either via direct input or by building a master file or similar
operation. The best way to avoid circular relationships is to not put
links on Summary Lines and not get overzealous in linking tasks.
If you are interested in a trace macro that allows you to see link
paths, you could take a look at Jack Dahlgren's trace macro. You can
find it on Jack's website at:
http://masamiki.com/project/macros.htm
It won't show you circular relationships, but it might help you manage
links you do have.
Hope this helps.
John
Project MVP