A family of Microsoft relational database management systems designed for ease of use.
Correct. 90ed is 90 calendar days ignoring the Project calendars. You can use elapsed days, weeks for lag and durations.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
How do I set task predecessors to count calendar days instead of working days? I don't want the task itself to schedule in calendar days, I
just want it to count off 90 calendar days from the predecessor task. How can I do this?
For instance:
Task 3 has a start date of 6/3/2013 and a duration of 1 day.
Task 8 has a duration of 2 days with task 3 as a predecessor set as 3FS+90 Days. It displays the start date as 10/8/13 which is 127 calendar days. I want it to be 90 calendar days or the date should be Monday 9/2/2013. This is 90 calendar days which will fall on a Sunday and then schedules the task to begin on the next working day.
Please let me know how to do this. Let me know if I can provide any more information.
Thanks,
Ben
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
Correct. 90ed is 90 calendar days ignoring the Project calendars. You can use elapsed days, weeks for lag and durations.
A buddy of mine suggested using edays instead of days on my predecessor call out, i.e. 3FS+90edays. This appears to work because edays are elapsed days.
Thanks for the response.
Hi,
I suggest you add a Milestone (0d) with a Calendar "calender" linked to the predecessor task then to link it to your task without lag:
Task3 Start 6/03 Finish 7/03
Milestone8 Start 90d calendar after Task3 Finish
Task8 Start the next working day of Milestone8
Hope it will help