Hi

I am using 2010 professional in a server environment, in the top half of our schedule template we have some stage durations which have cost resources assisgned and the dates and costs from these tasks are pulled into a status report through BI.


The top half is basically a report and the users need to adjust stage start and end dates on a regular basis.
My question is, does the duration always take priority when amending dates, i.e. if you shift out an end date manually, the duration is honoured and pulls the start date out too. Can I change this so that the start date doesnt move.
Basically these dates are constraints purely for the benefit of the status report, I can use manually scheduled tasks but then you cannot adjust the budgets for the tasks so they have to be auto.
I need the use to amend a start date or end date and reflect the new duration, not honour it and pull either the end or start with it?
I know this wont make scheduling sense, its purely for reporting.
Thanks
SP

Hi seanpears99,

No, sorry. No combination of task type is going to allow you to chance dates manually and increase duration. When you manually enter a finish date, Project sets a FNET (finish no earlier than) constraint, maintains the duration, and moves the start date.

The only work around would be to set the task at a low level (1%) complete which sets an Actual Start date. If you then change finish date, the start date will not move.