P5 - completed predecessors driving activities?

Not seen this BUT a colleague I respect has.

Do you have an example you can send me?

What has Primavera said about it?

try playing with Progress Override and Retained Logic

The following reasons are a check list of all the things that I cal think off that will cause an activity not to sit on the data date:

1. An activity calendar non work period after the Data Date
2. A resource on a Resource Driven activity with a calendar non work period after the Data Date
3. A constraint after the Data Date
4. A levelled schedule where an activity has been delayed
5. A predecessor with or without lag from an incomplete activity
6. A predecessor with or without lag from a completed activity in the future when the Scheduling Options are set to acknowledge a completed activity in the future relationship.
7. A predecessor with lag from a completed activity in the past. Check the scheduling options when a SS relationship is being used.
8. The activity is assigned an actual start in the future.
9. A relationship from another project.
10. A corrupt file which I have seen in all file types. Delete the activity and recreate it usually does the trick.

Paul E Harris
Eastwood Harris Pty Ltd, Melbourne, Australia
Planning and Scheduling Training Manual & Book Publishers, Consulting and Training
www.eh.com.au

Thanks guys esp. Paul for the comprehensive response.

After much pulling of hair, I have finally cracked it.

The schedule which I inherited has a start milestone for each area which is linked to other schedules in our company. These milestones were previously tasks with resources loaded. My predecessor converted these to milestones but did not delete the resources, most of which were driving.
As all these milestones have become actual in the past couple of weeks, they were pushing out the successors well beyond the data date even though all their predecessors were 100%.
By changing the milestones back to tasks, deleted the resources, and changing back to milestones, solved the problem.
V. strange.
Thanks again.
V