Hi,
As for the decimal durations, do verify Faq 5. in the FAQS (address below)
As for successors not immediately following predecessors, there could be
several reasons for this to happen:
1) Calculation is set to manual. Go to tools menu / option / scheduling tab
and set it to automatic or press F9 to recalculate.
2) The start date of the successor could be fixed by a strong constraint
such as Must Start On, Must Finish On, or Finish no later than. The
default option is that in a scheduling conflict situation, Project considers
these constraints as more compelling than the link and thus will not move
the
start date of the successor.
This setting can be changed sub Tools, Options, Schedule, "Tasks will
always honor their constraint dates"
3) The start date of the successor could be fixed by its actual start date.
This happens if it has any progress recorded to it.
4) The start date of the successor is later than the predecessor's
finish date. This can happen due to several reasons:
- When the successor has a "Start Not earlier than" or a "Finish not earlier
than" constraint;
- It can be due to another link to the successor
- It can happen because the successor is part of a summary task which is
- forced to start later by a constraint or a link (this is one good reason
not
to link to summary tasks).
- When the resource(s) assigned to the Task is (are) not available
To better understand this, remember that Finish to Start links only tell
Project that the successor can not start before the finish of the
predecessor and they don't imply an "equal to" relationship at all.
Similarly, in case of a Start to Start link, the start of the predecessor
will not always match the start of the predecessor; the same reasons may
apply.
Hope this helps
