Additional Options  
 When this check box is selected, 
holiday 
 definitions are considered during scheduling; otherwise, all holidays 
 are ignored.  Note that this option is disabled if no holidays have 
 been defined.  This option is automatically activated when holidays 
 are initially created.
 
 When this check box is selected, 
calendar 
 definitions are considered during scheduling; otherwise, all calendars 
 are ignored.  Note that this option is disabled if no calendars have 
 been defined.  This option is automatically activated when calendars 
 are initially created.
 
 When this check box is selected, the scheduling algorithm calculates a 
 separate 
critical path for each 
 
supertask in the project.
 
By default, the project's early finish time is treated as the 
 starting point for the calculation of 
 the backward pass 
 (which calculates the late start schedule).  The late finish 
 time for each supertask 
 is then determined during the backward pass on the basis of the precedence constraints. 
 If a target date is placed on the finish time of 
 a supertask, the late finish time of the supertask is further constrained by 
 this value.  However, when this option is activated, the scheduling algorithm 
 requires that the late finish time of each subtask be less than or equal 
 to the early finish time of the supertask.
 
 When this check box is selected, the scheduling algorithm uses the specified 
 
supertask duration 
 to compute the maximum allowed 
late finish time for each 
 supertask. Otherwise, the maximum allowed late finish time is determined by 
 the supertask span, as computed from the span of all the 
 
subtasks of the supertask.
 
 When this check box is selected, the resource requirements for all 
 
supertasks are used only for aggregation 
 purposes and not for 
resource-constrained scheduling.
 
 When this check box is selected, the resource requirements for all 
 
supertasks are ignored.
 
 When this check box is selected, the scheduling algorithm allows activities that 
 are completed or in progress to have nonzero float.  For more information about float, see 
 
total float and 
free float 
 in 
Appendix A, "Glossary of Project Management Terms." 
 By default, all completed or in-progress activities have zero float.
 
 When check box is selected, the scheduling algorithm assumes automatic 
 completion (or start) of activities that are 
predecessors 
 to activities already completed (or in progress).  For example, if activity B 
 is a successor of activity A, and B has an 
actual start 
 time (or 
actual finish time or both) specified 
 while A has no actual start or actual finish time, then the algorithm 
 assumes that A must have already finished.  Activity A is assigned an actual 
 start time and an actual finish time consistent with the precedence constraints.
 
 When check box is selected, the scheduling algorithm allows activities 
 that are in progress at the 
timenow date to be 
 split if they cause resource infeasibilities.  During resource allocation, any 
 activities with 
early start values less than the 
 timenow date are scheduled even if there are not enough resources.  This is 
 true even for activities that are in progress.  This option permits an activity 
 to be split into two segments at the timenow date, allowing the second segment 
 of the activity to be scheduled later when resource levels permit.  Note that 
 activities with a 
target date
alignment type of mandatory start or mandatory 
 finish are not allowed to be split; also, activities without resource 
 requirements are not split.