force edays-driven task to start in working time

S

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?
 
D

Dave

scottrogers said:
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?
 
D

Dave

Dave said:
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?
 
S

scottrogers

scottrogers said:
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?
 
S

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.
 
S

scottrogers

Dave said:
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
 
M

Mike Glen

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

Mike Glen
Project MVP
 
J

JulieS

scottrogers said:
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
 
S

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!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top