synching predecessor and successor dates based on F-S link

[Jim]

Hi folks,

I'm working with MSP2003 and PS2003. I have a project with afew tasks that have predecessor - successor relationships. They are F-S. Some have a lag, some have a lead time, some have neither. The issue I have is that when the finish date changes for a predecessor task, the start date for the successor remains unchanged. I've checked the calculation settings and it is set to recalculate automatically.

For example

Task 115 is a predecessor for task 117. T115's end date is June 28. T117's start date is June 30. If I change T115's end date to July 7, the startdate for T117 remains set to June 30.

Thanks for any insights.

Jim

 

[Mark Durrenberger]

Jim

Task 115 is a predecessor for task 117. T115's end date is June 28.

T117's start date is June 30. If >I change T115's end date to July 7, the
startdate for T117 remains set to June 30.

Make sure that there are not constraints on either task such as "Must Start
on" or "Must finish on" - the constraint for all tasks should be "As soon as
possible" (Specifically look at T117)

You can add a column to any view called "Constraint" to see how each
activity is set or you can double click on a task to bring up the task
dialog and switch to the "Advanced" tab and look at the Constraint type
field and the constraint date field

Hope that helps, let us know how it goes.
Mark


--
_________________________________________________________
Mark Durrenberger, PMP
Principal, Oak Associates, Inc, www.oakinc.com
"Advancing the Theory and Practice of Project Management"
________________________________________________________

The nicest thing about NOT planning is that failure
comes as a complete surprise and is not preceded by
a period of worry and depression.

- Sir John Harvey-Jones

Hi folks,

I'm working with MSP2003 and PS2003. I have a project with afew tasks

that have predecessor - successor relationships. They are F-S. Some have a
lag, some have a lead time, some have neither. The issue I have is that
when the finish date changes for a predecessor task, the start date for the
successor remains unchanged. I've checked the calculation settings and it
is set to recalculate automatically.

For example

Task 115 is a predecessor for task 117. T115's end date is June 28.

T117's start date is June 30. If I change T115's end date to July 7, the
startdate for T117 remains set to June 30.

 

[Jan De Messemaeker]

Adding to Mark's reply, you may have set the Actual Start of 117.
Project does not reschedule actuals.
HTH

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/index.htm
32-495-300 620

Hi folks,

I'm working with MSP2003 and PS2003. I have a project with afew tasks

that have predecessor - successor relationships. They are F-S. Some have a
lag, some have a lead time, some have neither. The issue I have is that
when the finish date changes for a predecessor task, the start date for the
successor remains unchanged. I've checked the calculation settings and it
is set to recalculate automatically.

For example

Task 115 is a predecessor for task 117. T115's end date is June 28.

T117's start date is June 30. If I change T115's end date to July 7, the
startdate for T117 remains set to June 30.

 

[Mark Durrenberger]

Ah yes. Forgot that one...
Mark


--
_________________________________________________________
Mark Durrenberger, PMP
Principal, Oak Associates, Inc, www.oakinc.com
"Advancing the Theory and Practice of Project Management"
________________________________________________________

The nicest thing about NOT planning is that failure
comes as a complete surprise and is not preceded by
a period of worry and depression.

- Sir John Harvey-Jones