(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?
(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.
MS Projects tells me when I open my planning that:
No calculation can be performed because of a circular relationship. Successors of task 462 refer back to this task (Or as I assume one of its subtasks) or its predecessors.
Now this include quit a lot of possible tasks which may cause this circular relation. Is there a smart way to find them?
Many thanks in advance for any help.
Martin
Printer-friendly version
Send to friend
Tom,
Meanwhile did more or less what you suggest in your reply. I found that I had lets say Summary task A as a predecessor of summary task B and meanwhile I had also sub-tasks of A being the predecessor of sub-tasks of B. Once I had cleaned that up the message did not re-appear. So leason learned there.....!!!
Martin,
I haven't seen that "No calculation can be performed..." error since at least MSP 2003. More recent editions of MSP make it very difficult to introduce circular logic through the user interface.
Most circular logic mistakes in MSP result from assigning logic to summary tasks - or more precisely, mixing parent-child task inheritence logic with explicit sequential logic. Your paranthetical remark implies this may be the case for you. The easiest and best solution overall is to remove all predecessors and successors from summary tasks. (E.g. Temporarily insert columns for "Predecessors", "Successors", and "Summary" into a bar chart view; Apply a pull-down filter to show only tasks where "Summary" is "Yes;" then clear predecessors and successors lists for all the summary tasks.)
In the absence of summary logic, you could manually trace down the sequencing mistake using the task detail form (predecessors and successors shown) or the network diagram view. I use a logic-tracing add-in of my own creation that does the job handily using a truncated logic trace. I wrote about it here: http://wp.me/p6CCB4-82.
Email: PPadmin@planningplanet.com
Replies