Difference between revisions of "Microsoft KB Archive/103139"

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 1: Line 1:
 
{|
 
{|
 
|width="100%"|
 
|width="100%"|
== Project Err Msg: "Late Date" with Start to Finish Relationship ==
+
== Project Err Msg: "Late Date" with Start to Finish Relationship ==
 
|}
 
|}
  
Line 41: Line 41:
 
== MORE INFORMATION ==
 
== MORE INFORMATION ==
  
&quot;X&quot;, the task mentioned in the late date message, can be used to find the pair of tasks that have the SF relationship. Keep in mind the following general rule, which holds in all cases: the predecessor to the task mentioned in the message is involved in a SF relationship.<br />
+
"X", the task mentioned in the late date message, can be used to find the pair of tasks that have the SF relationship. Keep in mind the following general rule, which holds in all cases: the predecessor to the task mentioned in the message is involved in a SF relationship.<br />
 
<br />
 
<br />
 
The two more-specific rules follow:<br />
 
The two more-specific rules follow:<br />
Line 56: Line 56:
 
# Give task1 and task2 a SF relationship, and give task2 and task3 a FS relationship.
 
# Give task1 and task2 a SF relationship, and give task2 and task3 a FS relationship.
  
A &quot;late date&quot; error message will be produced.
+
A "late date" error message will be produced.
  
 
Additional query words: 4.0 3.00a
 
Additional query words: 4.0 3.00a

Latest revision as of 08:25, 20 July 2020

Project Err Msg: "Late Date" with Start to Finish Relationship

Q103139

kbusage kberrmsg



The information in this article applies to:


  • Microsoft Project for Windows, versions 3.0, 3.0a, 4.0
  • Microsoft Project for the Macintosh, versions 3.0, 4.0





SYMPTOMS

If a task has a Start to Finish (SF) relationship with its predecessor, and this task has successor tasks with Finish to Start (FS) or Finish to Finish (FF) relationships that are involved in a chain of successors that span to the project end date, a late date message will be generated (while scheduling the project from Start).

Although the constraints are As Soon As Possible (ASAP) and there is no negative slack, there is a unique problem when using the SF relationship that will cause the following error message:

Late date before scheduled date in task x. The task cannot be completed in the time allocated. Choose the Help button....

This is not the expected behavior.



MORE INFORMATION

"X", the task mentioned in the late date message, can be used to find the pair of tasks that have the SF relationship. Keep in mind the following general rule, which holds in all cases: the predecessor to the task mentioned in the message is involved in a SF relationship.

The two more-specific rules follow:


  • Task x is the successor in the SF relationship if task x is also a predecessor in a FS relationship.
  • Task x is a successor with a FF relationship to a task that has the SF relationship with a predecessor.

Steps to Reproduce Behavior

  1. Enter three tasks, task1, task2, and task3, giving each a one day duration.
  2. Give task 1 a Start-No-Earlier-Than constraint that is two or more days later than the start date of the project.
  3. Give task1 and task2 a SF relationship, and give task2 and task3 a FS relationship.

A "late date" error message will be produced.

Additional query words: 4.0 3.00a

Keywords :
Issue type : kbprb
Technology : kbHWMAC kbOSMAC kbProjectSearch kbProject400Mac kbProjectMacSearch kbProject300Mac kbProject300 kbProject300a kbProject400


Last Reviewed: November 5, 2000
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.