Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 113817 - Last Review: September 18, 2011 - Revision: 6.0
A recurring task is rescheduled in Project if the summary task has a predecessor
This article was previously published under Q113817
In Microsoft Project, if a summary recurring task has a predecessor, and you change the Start date of the predecessor to a later date, the first
occurrence of the recurring task is scheduled for a different day than the one originally scheduled. If the predecessor task slips far enough in the future, eventually all occurrences of the recurring task will be scheduled to a different date and all occurrences will be on the same date.
For example, if you insert a weekly recurring task that occurs every Tuesday, and you link the summary recurring task to a predecessor task with a duration of one day that starts on a Monday, if you then move the predecessor task to Wednesday, the first occurrence of the weekly recurring task is scheduled for Thursday instead of the next Tuesday.
Each occurrence of a recurring task gets scheduled with a
Start No Earlier Than constraint. There are, however, no task dependencies between each occurrence to force each occurrence to always maintain a set amount of lag from its preceding occurrence. Therefore, as dates push later, the slack time between each occurrence is reduced until all occurrences begin on the same date.
To move a summary recurring task and all the recurring task occurrences as
a group, do the following:
Microsoft Project 98/2000
- Select the summary recurring task.
- From the Project menu, choose Recurring Task
Information.
- Under Length, in the From box, enter the new start date
for the recurring task. Choose OK.
APPLIES TO
- Microsoft Office Project Professional 2007
- Microsoft Office Project Standard 2007
- Microsoft Office Project Professional 2003
- Microsoft Office Project Standard 2003
- Microsoft Project 2002 Professional Edition
- Microsoft Project 2000 Standard Edition
- Microsoft Project 98 Standard Edition
- Microsoft Project 4.1 Standard Edition
- Microsoft Project 4.0 Standard Edition
- Microsoft Project 4.0 for Macintosh
| kbbug kbpending kbusage KB113817 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate