Fill Down Places Constraint on Task
  
PSS ID Number: Q137546
Article last modified on 10-24-1995
 
4.10
 
WINDOWS
 

--------------------------------------------------------------------
The information in this article applies to:
 
 - Microsoft Project for Windows, versions 3.0, 3.0a, 4.0, and 4.1
 - Microsoft Project for the Macintosh, versions 3.0, 4.0
--------------------------------------------------------------------
 
SYMPTOMS
========
 
When you use the Fill Down command to create a task, the new task may
receive a constraint other then As Soon As Possible (ASAP).
 
CAUSE
=====
 
This behavior occurs if you have selected the start or finish field as a
part of the fill down process. The constraint that is created is dependent
on the order of these two fields in your table. For example, if the Finish
field is after the Start field and both fields are selected, the constraint
will be Finish No Earlier Than (FNET) since the finish date is entered
after the Start date. If the order of the fields is reversed, Finish then
Start, the constraint will be Start No Earlier Than (SNET).
 
WORKAROUND
==========
 
To use the Fill Down command, without incurring a constraint, remove the
Start and Finish columns from the table or don't select these columns. This
will allow an ASAP constraint.
 
KBCategory: kbusage
KBSubcategory:
 
Additional reference words: 4.10
=============================================================================
Copyright Microsoft Corporation 1995.
