![]() |
|
|
|
#1
|
|||
|
|||
|
When you schedule a project from a finish date, all tasks are constrained with an As Late As Possible constraint. so even though you have a S to S link between Task 1 and Task 2, it is still constrained with ALAP. Change the constraint to ASAP and it will honor the S to S relationship. Constraints are stronger than links. |
|
#2
|
|||
|
|||
|
Thanks.
But I already changed all tasks in the respective phase to have the ASAP constraint, and still it won't honor the predecessor. |
|
#3
|
|||
|
|||
|
Tasks don't obey predecessors if:
There are constraints There are actual dates against the tasks Can you post a copy of the file so I can look? or post a screen shot as an attachment? |
|
#4
|
|||
|
|||
|
Hi Julie,
See attached file. The area I keep having problems with is the Summary Task "Design" and all its subtasks. Despite the "Schedule from Project End Date", the tasks need to start as soon as possible, on or after 25.08. The project is purely milestone driven, duration is not driving in this case. I figured giving Line 3 a Start No Later than 25.08. constraint and Line 5 a "3SS" dependency would do the trick, but it won't. Maybe I'm missing something fundamentally, but I got it to work before (see attached screenshot). Line 3 has a SNLT constraint of 25.08. and all others seemingly fall into line with a ASAP constraint. |
|
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| using a predecessor twice | ketanco | Project | 2 | 03-07-2014 04:52 PM |
Predecessor name displayed in a text field
|
Leah | Project | 7 | 02-07-2014 03:26 PM |
| Linking predecessor twice | ketanco | Project | 1 | 04-06-2012 08:49 AM |
| MS Project 2007 Predecessor Macro | dmpyne | Project | 1 | 12-14-2011 08:46 AM |
New to project - Predecessor Question
|
geissap | Project | 1 | 01-20-2011 10:00 AM |