force edays-driven task to start in working time

[scottrogers]

I have 2 linked tasks in Project 2003 similar to the following example:

Task 100: finishes Wed 1/30/08
Task 101: predecessor 100FS+4edays --> shows start date of Sun 2/3/08

Is there anyway to force task 101 to start only on days designated as
working time?

 

[Dave]

I have 2 linked tasks in Project 2003 similar to the following example:

Task 100: finishes Wed 1/30/08
Task 101: predecessor 100FS+4edays --> shows start date of Sun 2/3/08

Is there anyway to force task 101 to start only on days designated as
working time?

Put a milestone between the tasks?

 

[Dave]

Put a milestone between the tasks?

On reflection, I'm talking nonsense, this should work automatically.
The calendar should take care of it without any further work.

Is the Sunday a non-working day in the calendar and are there no task
calendars applied?

 

[Mike Glen]

Hi scottrogers ,

Welcome to this Microsoft Project newsgroup

Try removing the e from edays.

FAQs, companion products and other useful Project information can be seen at
this web address: http://project.mvps.org/faqs.htm

Hope this helps - please let us know how you get on

Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for Project Tutorials


wrote:

 

[scottrogers]

Put a milestone between the tasks?

I guess that would work, but I have tens if not hundreds of these
relationships in my schedule, and I don't want to have to add and maintain
fake milestones for each one. Isn't there a better way?

 

[scottrogers]

This approach won't work either since the edays relationship (vice straight
days) was intentional - I have a requirement for task 101 to occur 4 calendar
days after task 100 but it can't occur on a non-business day.

 

[scottrogers]

On reflection, I'm talking nonsense, this should work automatically.
The calendar should take care of it without any further work.

Is the Sunday a non-working day in the calendar and are there no task
calendars applied?

Yes, I'm using the default Standard (Project Calendar) that shows all
weekends (Saturday and Sunday) as non-working time.

Although now that I look at it, the only eday relationships that are screwed
up are those where the successor task is a milestone. In the example above,
task 100 is a regular task and 101 is a milestone. As far as I can tell, it
does work correctly for task-to-task eday relationships

 

[Mike Glen]

That what the ordinary setting for days does - can only be done on a
workday.

Mike Glen
Project MVP

 

[JulieS]

This approach won't work either since the edays relationship (vice
straight
days) was intentional - I have a requirement for task 101 to occur 4
calendar
days after task 100 but it can't occur on a non-business day.

Hello scott,

Because milestones have no duration, that do not conform to working
versus non-working issues. Change the duration of your milestone
(Task 101) to 1 minute and it will move to a working day. You can
also format the task to show as a milestone.

I hope this helps. Let us know how you get along.

Julie
Project MVP

Visit http://project.mvps.org/ for the FAQs and additional information
about Microsoft Project

 

[scottrogers]

That appears to work. It does louse up the handful of backward links (such as
100FS-30edays) since it causes them to slip a day as well, but I fixed that
by adding an extra day to all the lag links. Thanks!

 

[JulieS]

You're welcome Scott and thanks for the feed back.

Julie
Project MVP