We are currently using MSP2003 and are looking to move to MSP 2013, but I notice that the Update Project function (Tools, Tracking, Update Project in MSP2003) doesn’t work the same in MSP2013 as it does in MSP2003.
In MSP2003, if I set the task to Fixed Units and select Update Project and select “Reschedule uncompleted work to start after:” and put the status date in for the date, then select “Selected tasks”, the remaining work on the task will remain as it was before and be rescheduled from the status date, and the end date of the task will change to allow the work to be scheduled for the resources keeping the units the same.
In MSP2013 (and MSP2010), if I select the same options as above, the work will be rescheduled from the status date, the end date of the tasks remains the same and the util (peak) remain the same but the remaining work will change.
How can I make MSP2013 behave the same as MSP2003? I want to reschedule the task from the status date, keeping the utilisation (peak) and the remaining work the same and have MSP recalculate the end date? If I change the task to Fixed Work, the work and end date will remain the same but the utilisation of the resources will change. So there appears to be no way to force MSP to recalculate the end date of task and keep the work and utilisation of the resources the same.
We actually use the MSP function “UpdateProject” in a macro to update the task, and I couldn’t understand why I was getting different results in MSP2013, so I thought I would investigate the function and found that it is treated differently in MSP2013 (and MSP2010) – as explained above.
Any help would be most appreciated.