Microsoft KB Archive/102617

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:13, 12 August 2020 by X010 (talk | contribs) (X010 moved page Microsoft KB Archive/Q102617 to Microsoft KB Archive/102617 without leaving a redirect: Text replacement - "Microsoft KB Archive/Q" to "Microsoft KB Archive/")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Finish To Finish and Start To Finish Relationship Ignored

PSS ID Number: Q102617 Article last modified on 03-15-1995

1.00 3.00 3.00a | 1.10 3.00

WINDOWS | MACINTOSH

The information in this article applies to:
- Microsoft Project for Windows, versions 1.0, 3.0, 3.0a - Microsoft Project for the Macintosh, versions 1.1, 3.0

SUMMARY

A Finish To Finish relationship and a Start To Finish relationship between two tasks is ignored if the successor task has a Finish No Later Than constraint even though the constraint does not violate the relationship. With this arrangement, the successor task will move to the start of the project, or locate itself with a predecessor task that has a Finish To Start or Start To Start relationship.

NOTE: This behaviour does not occur in later versions of Microsoft Project.

MORE INFORMATION

No other constraints that do not supersede the relationship have this effect. Finish No Earlier Than, Start No Earlier Than, and Start No Later Than do not cause Microsoft Project to ignore the relationship.

Steps to Reproduce Behavior

  1. Create three tasks, “task1”, “task2”, and “task3” with three day (3d), two day (2d), and one day (1d) duration, respectively.
  2. Make task1 a predecessor of task2 with a finish-to-start relationship. Make task2 a predecessor of task3 with a finish-to-finish or start-to-finish relationship. Task3 is now scheduled to either start or finish at the same time as task2 (as it should be).
  3. Apply a constraint of Finish No Later Than using a date that is far into the future such as 1/1/95.

Results

Task3 is rescheduled (ignoring the Finish To Finish or Start To Finish relationship with task2). Removing the Finish No Later Than constraint on task3 causes it to be correctly rescheduled.

KBCategory: kbusage KBSubcategory:

Additional reference words: 3.00 3.00a 1.10 1.00

Copyright Microsoft Corporation 1995.