Primavera P6 V2
I have been having some issues recently in P6 where the software is remembering old dates and using these old dates to drive successors rather than the correct logic being the driver.
Basically I have some milestones linked to activites in my schedule and the milestones are being held out at a previous date despite the predecessor activities having moved to an earlier date.
For example; activity A was previously finishing on 25th May but is now finishing on 20th May but the successor milestone is still being held out on the 25th May.
I have checked the obvious solutions such as calendar assignment, no constraints, etc but the only way to correct it is to delete the activity and create a new one (at which point you have to re-assign all activity codes). It does not work just copying the existing activity and pasting as it still remembers the old dates!
Has anyone come accross this before and is there a solution or do I just need to accept it is one of P6's little quirks?
Many Thanks
Ben
Replies