FS Relationship not working (long)

[CM WM]

I have a task (ASAP constraint) with FS relationship to three predecessors.
The latest of all three predecessors finishes on 6 Sep 07. But the task in
question starts on 24 Sep 07.

If I change the constraint to ALAP and then back to ASAP, the task moves to
6 Sep 07, as expected.

The Early Start date for this task is correct (6 Sep 07 - the date that the
last predecessor finishes). But the start date is 24 Sep 07, and the Late
Start date is 17/12/07.

I've checked that I don't have any predecessors associated with summary
tasks. The fact that changing the task to ALAP (or MFO or MSO or FNET or
SNET) and then immediately back to ASAP tends to indicate there is nothing
obvious holding it out.
Interstingly, it isn't fixed if I change the constraint to FNLT or SNLT (and
allow the subsequent conflicts) and then change it back.

I've tried opening it on another PC in case my softwre is corrupt, but it
behaves the same way.... as do several other tasks around this one.

Calculation is set to automatic; "Autolink Inserted or Moved Tasks" is set
to off; I'm using MS Project Standard 2003 11.0.2003.0816.15. This is only
one task, but this problem is recurring throughout the rest of the project
(1000 tasks).

Leveling is set to "manual", and calculation is automatic. There are no
lags on the predecessors for this task. The single successor is FS+0d.

The Project Information window under the Project menu shows "Schedule from:
Project Start Date" and has text below stating "All tasks begin as soon as
posisble".

There are no non-working days (except for week ends) associated with the
Project Calendar or the Resouce Calendar associated with the resource for
this task. All Tasks have "none" nominated in the calendar field of the
Advanced tab in the Task Information dialogue box.

Can anyone help? Am I missing something simple? I can't find what is
holding this task out?

 

[CM WM]

It appears I haven't installed any service packs. I'll go and install SP3:
do you think this will fix the problem?

 

[Rod Gill]

It's always a starting point, otherwise you won't know if your problem is
real or already fixed!

--

Rod Gill
Project MVP

Project VBA Book, for details visit:
http://www.projectvbabook.com

NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx

 

[CM WM]

I've now updated to SP3. The problem persists (for example, I have a task ID
507 that starts on 19 Oct 07 and has one predecessor, task 54, which is a
milestone with a completion date of 5 Oct 07). Any ideas?

 

[JulieS]

Hello CM,

It appears as though you have eliminated the most obvious. If you would
care to, zip the file and send it to me via email and I'll see if I can
sleuth it out. No guarantees, but we could be sitting here forever
guessing. Send it to:
passport 6847 AT maine.rr.com

Remove the spaces and replace AT with @
I hope this helps. Let us know how you get along.

Julie
Project MVP

Visit http://project.mvps.org/ for the FAQs and additional information
about Microsoft Project

 

[JulieS]

For those of you following the saga, the short answer was that tasks had
been delayed by resource leveling. By resetting the leveling delay to
zero, Start = Early Start.

Julie
Project MVP