A
Adrian Dodd
Usually (depending on configuration) new tasks default to the start date of
the project. I have a MS2002 plan where (apparently out of the blue) new
tasks have started defaulting to a different future date which is neither
the start or end of the project (actually 12-feb-04). Because the date is in
the future the task doesn't react as required to dependencies on other tasks
i.e. a new task which is made dependant on another task in the plan with a
completion date in advance of say end January will have a start date of
12-feb-04. The task properties appear ok i.e. there are no dependencies and
the constraint type is 'as soon as possible'. Also the scheduling options
haven't changed i.e. new tasks start date is set to project start date. The
task can be forced to start on an earlier date by use of task constraints
(e.g. must start on) but that isn't a solution.
The problem also seems to depend upon the location of the new task within
the plan. If entered towards the top of the plan, the default dates are as
expected, but if inserted further down the plan the behaviour described
above is exhibited.
The problem may be related to constraint dates. In testing I have observed
that the problem appears to start happening following the display of a
scheduling conflict message.
Any idea of what is causing this - or more usefully how I can stop it
happening?
Many thanks
Adrian
the project. I have a MS2002 plan where (apparently out of the blue) new
tasks have started defaulting to a different future date which is neither
the start or end of the project (actually 12-feb-04). Because the date is in
the future the task doesn't react as required to dependencies on other tasks
i.e. a new task which is made dependant on another task in the plan with a
completion date in advance of say end January will have a start date of
12-feb-04. The task properties appear ok i.e. there are no dependencies and
the constraint type is 'as soon as possible'. Also the scheduling options
haven't changed i.e. new tasks start date is set to project start date. The
task can be forced to start on an earlier date by use of task constraints
(e.g. must start on) but that isn't a solution.
The problem also seems to depend upon the location of the new task within
the plan. If entered towards the top of the plan, the default dates are as
expected, but if inserted further down the plan the behaviour described
above is exhibited.
The problem may be related to constraint dates. In testing I have observed
that the problem appears to start happening following the display of a
scheduling conflict message.
Any idea of what is causing this - or more usefully how I can stop it
happening?
Many thanks
Adrian