Circular Reference

S

SteveR

I have experience a "Circular Reference" error a number of
times now and it seems as though the only way to get
around it is to delete the project from the database and
create it over again.

Has anybody experienced this problem and if so how did you
resolve?
 
C

Carl

There could be a number of reasons. What I have found is
that, if the scheduling warnings are turned off by the
P2002 user, project professional cannot resolve the logic
in the plan when opening, causing a full application error.

I have never found an easy way to resolve this. The best
i've managed is to recreate the plan by:

1_ Querying the database to return the task and resource
data to excel
2_ importing query results to project via a mapping and
recreating the file.

this does still leave some manual process to undertake to
get the plan back in shape.

Another alternative would be to query the db and see if
you can identify which pred/successor link is causing the
error.

I usually just fall back to a backup and handhold the user
thru.... id be interested if you hear of/find a better way
 
G

Gary L. Chefetz

Steve:

The best way to solve this problem is to avoid it. This is typically handled
by rethinking your strategy for using predecessor/successor relationships in
Project. Once these occur, the best way to fix the plan is track down the
circular relationship by tracing the work paths from the task number
reported in the error message. To turn a not so humanly possible task into a
piece of cake, check out Jack Dahlgren's site at http://www.masamiki.com and
download his trace macro.

--

Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.
 
Top