Reminder tasks
Featured Partner
Top Posters
Kristian Mcwilliams
1 posts
dagogo dan - jumbo
2 posts
Alex Lyaschenko
27 posts
James Williams
75 posts
xerxes
0 posts
edwin
0 posts
jhalluk69
0 posts
wilmoahyi
0 posts
Peter Holroyd
51 posts
Robert Guers
1 posts
Our Partners
Thanks!!!!!!!!
That works perfect
Thank you Thank you Thank you Thank you
Ben,
On the reminder activity, tick the zero free float in the constraints dialog box.
Regards,
Larry
Yes the block wall has a pred of the permit. But the permit doesnt have a pred. That is what is putting it at the data date. I have tried all the options in the task field and have not gotten any different results.
It is driving me crazy.
Ad Ben,
It will have a predecessor! The start of the wall is a predecessor of the finish of the getting the permit. With -30 days lag (lead).
If its date isnt moving as the walls dates move, something is wrong. Try making the block wall "reminder" a milestone, with duration of zero, and then have the activity to apply for the permit as a FS successor of that milestone.
If it doesnt work then, something else is going on.
Thanks for the reply.
I did try that.
What I am trying to do is set a reminder to get my block wall permit 30 days before I start the wall. So I did as you say and did a SF and even tried a SS with -30 lag and it still just sits at the data date since it has no pred. I dont want to put a pred. on it so that it will float with the wall. If I can start early or late, I still want to remember to get it 30 days before I start the wall.
Anyone????
Hi, Ad Ben.
I am by no means an expert on any software package (with apologies to Vladimir, none of them do all of what I want them to do, although Spider may come closest!).
However I would think that using the following logic relationship should do the trick:
A = Install Window
B = Order Window
Pred A start-to-finish -20 Succ B
A -> SF-20 -> B
One word of warning: if using MS Project, be aware that the late dates it computes for the successor in SF relationships are not intuitively obvious (IMO, they are one unit too great). In the above example, if A has an early (or late) start date of Day 50, it will give B a finish date of Day 30, when the finish of Day 29 is what IMO would be consistent with the usual approach of having activities always finish at the end of a time unit.
I dont know about Primavera, Spider, Open Plan, etc.