Need calendar days not work days duration for summary tasks?

[DWGLompoc]

For a government customer, I need to show "duration" in calendar days not
work days. The big problem is with "Summary Tasks". I can easily set
individual tasks to calendar days be specifying, for example, 5 edays
(elapsed days). But the summary task is still displaying work days. I've
tried a few things suggested in other posts. E.g., inserting new columns
"Duration 1", then using using tools have gone to the customize fields window
and selected for summary tasks select Sum. The summary task then sums all of
the durations as calendar days. The problem is that some of the tasks are
concurrent. This gives me an inflated duration for the summary task. Any
ideas.

 

[JulieS]

Hello DWGLompoc,

You can use a custom Duration field (Duration1 as you suggest) with
a custom calendar and a formula to calculate the difference between
the start and finish date of a task. Create a custom calendar where
Saturday and Sunday are working days in addition to Monday through
Friday. I've named mine 7Day.

Then customize the Duration1 field with the following formula:

ProjDateDiff([Start],[Finish],"7Day")

Make sure you set the summary tasks to "use formula" in the
customize field dialog box.

By using the formula you also avoid any potential issues caused by
using "edays" when assigning resources.

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

 

[DWGLompoc]

Does that mean I then have to enter the start/finish date for every task
rather than entering a duration?

Hello DWGLompoc,

You can use a custom Duration field (Duration1 as you suggest) with
a custom calendar and a formula to calculate the difference between
the start and finish date of a task. Create a custom calendar where
Saturday and Sunday are working days in addition to Monday through
Friday. I've named mine 7Day.

Then customize the Duration1 field with the following formula:

ProjDateDiff([Start],[Finish],"7Day")

Make sure you set the summary tasks to "use formula" in the
customize field dialog box.

By using the formula you also avoid any potential issues caused by
using "edays" when assigning resources.

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

For a government customer, I need to show "duration" in calendar
days not
work days. The big problem is with "Summary Tasks". I can easily
set
individual tasks to calendar days be specifying, for example, 5
edays
(elapsed days). But the summary task is still displaying work
days. I've
tried a few things suggested in other posts. E.g., inserting new
columns
"Duration 1", then using using tools have gone to the customize
fields window
and selected for summary tasks select Sum. The summary task then
sums all of
the durations as calendar days. The problem is that some of the
tasks are
concurrent. This gives me an inflated duration for the summary
task. Any
ideas.

 

[JulieS]

No, absolutely not. In fact, you really shouldn't be entering start
and finish dates. The start and finish date for each task should be
calculated by Project based upon the start date of the project, the
task duration and the predecessor/successor relationships throughout
your project. Those dates may be modified further through
constraints as well as resource calendars.

Julie

Does that mean I then have to enter the start/finish date for
every task
rather than entering a duration?

Hello DWGLompoc,

You can use a custom Duration field (Duration1 as you suggest)
with
a custom calendar and a formula to calculate the difference
between
the start and finish date of a task. Create a custom calendar
where
Saturday and Sunday are working days in addition to Monday
through
Friday. I've named mine 7Day.

Then customize the Duration1 field with the following formula:

ProjDateDiff([Start],[Finish],"7Day")

Make sure you set the summary tasks to "use formula" in the
customize field dialog box.

By using the formula you also avoid any potential issues caused
by
using "edays" when assigning resources.

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


message

For a government customer, I need to show "duration" in
calendar
days not
work days. The big problem is with "Summary Tasks". I can
easily
set
individual tasks to calendar days be specifying, for example, 5
edays
(elapsed days). But the summary task is still displaying work
days. I've
tried a few things suggested in other posts. E.g., inserting
new
columns
"Duration 1", then using using tools have gone to the customize
fields window
and selected for summary tasks select Sum. The summary task
then
sums all of
the durations as calendar days. The problem is that some of
the
tasks are
concurrent. This gives me an inflated duration for the summary
task. Any
ideas.

 

[DavidC]

One other option is to simply set the summary tasks calendar to the 7 day
week calendar.

Hope this helps

regards

DavidC

Does that mean I then have to enter the start/finish date for every task
rather than entering a duration?

Hello DWGLompoc,

You can use a custom Duration field (Duration1 as you suggest) with
a custom calendar and a formula to calculate the difference between
the start and finish date of a task. Create a custom calendar where
Saturday and Sunday are working days in addition to Monday through
Friday. I've named mine 7Day.

Then customize the Duration1 field with the following formula:

ProjDateDiff([Start],[Finish],"7Day")

Make sure you set the summary tasks to "use formula" in the
customize field dialog box.

By using the formula you also avoid any potential issues caused by
using "edays" when assigning resources.

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

For a government customer, I need to show "duration" in calendar
days not
work days. The big problem is with "Summary Tasks". I can easily
set
individual tasks to calendar days be specifying, for example, 5
edays
(elapsed days). But the summary task is still displaying work
days. I've
tried a few things suggested in other posts. E.g., inserting new
columns
"Duration 1", then using using tools have gone to the customize
fields window
and selected for summary tasks select Sum. The summary task then
sums all of
the durations as calendar days. The problem is that some of the
tasks are
concurrent. This gives me an inflated duration for the summary
task. Any
ideas.

 

[JulieS]

Good point David. The downside is that you would have to apply the 7Day task
calendar to all summary tasks, whereas the formula would automatically
calculcate.

Julie

One other option is to simply set the summary tasks calendar to the 7 day
week calendar.

Hope this helps

regards

DavidC

Does that mean I then have to enter the start/finish date for every task
rather than entering a duration?

Hello DWGLompoc,

You can use a custom Duration field (Duration1 as you suggest) with
a custom calendar and a formula to calculate the difference between
the start and finish date of a task. Create a custom calendar where
Saturday and Sunday are working days in addition to Monday through
Friday. I've named mine 7Day.

Then customize the Duration1 field with the following formula:

ProjDateDiff([Start],[Finish],"7Day")

Make sure you set the summary tasks to "use formula" in the
customize field dialog box.

By using the formula you also avoid any potential issues caused by
using "edays" when assigning resources.

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


For a government customer, I need to show "duration" in calendar
days not
work days. The big problem is with "Summary Tasks". I can easily
set
individual tasks to calendar days be specifying, for example, 5
edays
(elapsed days). But the summary task is still displaying work
days. I've
tried a few things suggested in other posts. E.g., inserting new
columns
"Duration 1", then using using tools have gone to the customize
fields window
and selected for summary tasks select Sum. The summary task then
sums all of
the durations as calendar days. The problem is that some of the
tasks are
concurrent. This gives me an inflated duration for the summary
task. Any
ideas.

 

[DWGLompoc]

Thanks all.

Good point David. The downside is that you would have to apply the 7Day task
calendar to all summary tasks, whereas the formula would automatically
calculcate.

Julie

One other option is to simply set the summary tasks calendar to the 7 day
week calendar.

Hope this helps

regards

DavidC

Does that mean I then have to enter the start/finish date for every task
rather than entering a duration?

:

Hello DWGLompoc,

You can use a custom Duration field (Duration1 as you suggest) with
a custom calendar and a formula to calculate the difference between
the start and finish date of a task. Create a custom calendar where
Saturday and Sunday are working days in addition to Monday through
Friday. I've named mine 7Day.

Then customize the Duration1 field with the following formula:

ProjDateDiff([Start],[Finish],"7Day")

Make sure you set the summary tasks to "use formula" in the
customize field dialog box.

By using the formula you also avoid any potential issues caused by
using "edays" when assigning resources.

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


For a government customer, I need to show "duration" in calendar
days not
work days. The big problem is with "Summary Tasks". I can easily
set
individual tasks to calendar days be specifying, for example, 5
edays
(elapsed days). But the summary task is still displaying work
days. I've
tried a few things suggested in other posts. E.g., inserting new
columns
"Duration 1", then using using tools have gone to the customize
fields window
and selected for summary tasks select Sum. The summary task then
sums all of
the durations as calendar days. The problem is that some of the
tasks are
concurrent. This gives me an inflated duration for the summary
task. Any
ideas.

 

[Paul Billings]

Good point David.  The downside is that you would have to apply the 7Day task
calendar to all summary tasks, whereas the formula would automatically
calculcate.

Julie

One other option is to simply set the summary tasks calendar to the 7 day
week calendar.

Hope this helps

regards

DavidC

Does that mean I then have to enter the start/finish date for every task
rather than entering a duration?
:
Hello DWGLompoc,
You can use a custom Duration field (Duration1 as you suggest) with
a custom calendar and a formula to calculate the difference between
the start and finish date of a task.  Create a custom calendar where
Saturday and Sunday are working days in addition to Monday through
Friday.  I've named mine 7Day.
Then customize the Duration1 field with the following formula:
ProjDateDiff([Start],[Finish],"7Day")
Make sure you set the summary tasks to "use formula" in the
customize field dialog box.
By using the formula you also avoid any potential issues caused by
using "edays" when assigning resources.
I hope this helps.  Let us know how you get along.
Julie
Project MVP
Visithttp://project.mvps.org/for the FAQs and additional
information about Microsoft Project
For a government customer, I need to show "duration" in calendar
days not
work days.  The big problem is with "Summary Tasks".  I can easily
set
individual tasks to calendar days be specifying, for example, 5
edays
(elapsed days).  But the summary task is still displaying work
days.  I've
tried a few things suggested in other posts.  E.g., inserting new
columns
"Duration 1", then using using tools have gone to the customize
fields window
and selected for summary tasks select Sum.  The summary task then
sums all of
the durations as calendar days.  The problem is that some of the
tasks are
concurrent.  This gives me an inflated duration for the summary
task.  Any
ideas.

On the other hand, using a 7Day calendar for summary tasks FIXES the
seeming inconsistency in the summary task Duration field. For a
concrete task, Duration=Work*Units -- always. Not so for a summary
task. Summary task durations also include leveling delays or SNET
constraints rendering that relation innacurate. IMO, it's better to
have summary durations always equal calendar duration.

Paul

 

[Jeff Magaoitin]

Well I had been typing this exact question in when I found this thread, but
the process listed above does not seem to be working for me. It is a bit
closer to displaying the correct calendar days, but something is still wrong
with my schedule.

I think that I have followed the directions above correctly. Under the Tools
menu I went to “Change Working Time†and created a New Calendar with the
Title “7day†then set Saturday and Sunday to the same working times as the
rest of the work days.

Then I added the Custom Field “Duration1†, changed the attributes to
“Formula†and entered the formula above. Under Calculation for Task and Group
Summary Rows, Clicked on “Use Formulaâ€

When I insert the row “Duration1†the displayed information is a bit closer
to the actual days, but is still off, now by fractions of a day.

As an example one row has a Start Date of 9/14/09, when I enter 5 days under
“Duration†it calculates 9/18/09 correctly (both the Duration and Duration1
columns display 5 days correctly). When I enter 6 days (adding the following
Working day, Monday), it calculated the finish date as 9/21/09 but the newly
added “Duration1†column now lists 7.25 days, instead of 8 calendar days.

With almost 200 line items the rounding of the days has me off by a large
number for the overall contract duration.

What have I done incorrectly to allow the new column to display .75 days off
from the actual total?

 

[JulieS]

"Paul Billings" wrote in message

On the other hand, using a 7Day calendar for summary tasks FIXES
the
seeming inconsistency in the summary task Duration field. For a
concrete task, Duration=Work*Units -- always. Not so for a summary
task. Summary task durations also include leveling delays or SNET
constraints rendering that relation innacurate. IMO, it's better
to
have summary durations always equal calendar duration.

Paul

Hello Paul,

I'm not sure I follow you completely. True, Work = Duration *
Assignment Units, but you shouldn't have resource assigned to
summary tasks, so assignment units doesn't play into this.

You can certainly see a difference between durations on subtasks
versus duration on summary tasks due to differences in calendars
used to define the "working" time used in Duration. For example:
A project with 3 Aug 2009 as the start date.
Two tasks (Task A & Task B) both with two days duration linked F to
S.
Summary task duration = 4 days
Task A start Monday 3 Aug 2009 end Tuesday 4 Aug 2009
Task B starts Wednesday 5 Aug 2009, ends Thursday 6 Aug 2009

Create 2 resources:
Resource 1 only work M, W, F
Resource 2 works T, TH

Assign Resource 1 to Task A
Task A duration = 2 days, starts on Mon 3 Aug but now ends on Wed 5
Aug
Task B start date shifts to Thurs Aug 6 and ends on Friday Aug 7

The summary task duration is now 5 days.
The project calendar has Tuesday as a working day, so the non
working day for Resource 1 assigned to Task a is "counted" for the
duration.

Assign Resource 2 to Task B
The duration of Task 2 still shows as 2 days but the task now ends
on Tuesday 11 Aug

The summary task duration = 7 days which is equal to the span from
Monday (3 August) morning through Tuesday (11 August) afternoon not
counting Saturday and Sunday which are nonworking days on the
project calendar.

Julie

 

[JulieS]

Hello Jeff,

A couple of things -- first show date and time in your start date
and finish date through Tools > Options, View tab. Double check the
start and finish times of your task. Do they start and end at the
beginning (8:00 am) and the end (5:00 pm) of the work day?

What are your working times in your calendar? (Tools > Change
Working time)?
What is your definition of the number of hours in a day (Tools >
Option, Calendar tab)

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

 

[DavidC]

Hi Julie,

I find the easiest way is to simply filter for all Summary tasks, open the
task calendar field, change the calendar for the first summary task to the 7
day week calendar, then simply drag to copy that cell through all the
remaining summary tasks. I find that the field only updates those activities
that can be seen, so as long as the only 'tasks' showing are the summary
tasks then all the summary tasks will have a 7 day calendar assigned to them.
The advantage IMHO is that it is simple and quick, does not expose the user
to potential errors in the formula.

Just feel that the old 'KISS' prinicple is always a good starting point.

Regards

DavidC

Good point David. The downside is that you would have to apply the 7Day task
calendar to all summary tasks, whereas the formula would automatically
calculcate.

Julie

One other option is to simply set the summary tasks calendar to the 7 day
week calendar.

Hope this helps

regards

DavidC

Does that mean I then have to enter the start/finish date for every task
rather than entering a duration?

:

Hello DWGLompoc,

You can use a custom Duration field (Duration1 as you suggest) with
a custom calendar and a formula to calculate the difference between
the start and finish date of a task. Create a custom calendar where
Saturday and Sunday are working days in addition to Monday through
Friday. I've named mine 7Day.

Then customize the Duration1 field with the following formula:

ProjDateDiff([Start],[Finish],"7Day")

Make sure you set the summary tasks to "use formula" in the
customize field dialog box.

By using the formula you also avoid any potential issues caused by
using "edays" when assigning resources.

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


For a government customer, I need to show "duration" in calendar
days not
work days. The big problem is with "Summary Tasks". I can easily
set
individual tasks to calendar days be specifying, for example, 5
edays
(elapsed days). But the summary task is still displaying work
days. I've
tried a few things suggested in other posts. E.g., inserting new
columns
"Duration 1", then using using tools have gone to the customize
fields window
and selected for summary tasks select Sum. The summary task then
sums all of
the durations as calendar days. The problem is that some of the
tasks are
concurrent. This gives me an inflated duration for the summary
task. Any
ideas.

 

[JulieS]

I agree David. The advantage with the task calendar is the
indicator in the indicator column. Nice visual and reminder if
you've missed anything.
Julie

Hi Julie,

I find the easiest way is to simply filter for all Summary tasks,
open the
task calendar field, change the calendar for the first summary
task to the 7
day week calendar, then simply drag to copy that cell through all
the
remaining summary tasks. I find that the field only updates those
activities
that can be seen, so as long as the only 'tasks' showing are the
summary
tasks then all the summary tasks will have a 7 day calendar
assigned to them.
The advantage IMHO is that it is simple and quick, does not expose
the user
to potential errors in the formula.

Just feel that the old 'KISS' prinicple is always a good starting
point.

Regards

DavidC

Good point David. The downside is that you would have to apply
the 7Day task
calendar to all summary tasks, whereas the formula would
automatically
calculcate.

Julie

One other option is to simply set the summary tasks calendar to
the 7 day
week calendar.

Hope this helps

regards

DavidC

:

Does that mean I then have to enter the start/finish date for
every task
rather than entering a duration?

:

Hello DWGLompoc,

You can use a custom Duration field (Duration1 as you
suggest) with
a custom calendar and a formula to calculate the difference
between
the start and finish date of a task. Create a custom
calendar where
Saturday and Sunday are working days in addition to Monday
through
Friday. I've named mine 7Day.

Then customize the Duration1 field with the following
formula:

ProjDateDiff([Start],[Finish],"7Day")

Make sure you set the summary tasks to "use formula" in the
customize field dialog box.

By using the formula you also avoid any potential issues
caused by
using "edays" when assigning resources.

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


message
For a government customer, I need to show "duration" in
calendar
days not
work days. The big problem is with "Summary Tasks". I
can easily
set
individual tasks to calendar days be specifying, for
example, 5
edays
(elapsed days). But the summary task is still displaying
work
days. I've
tried a few things suggested in other posts. E.g.,
inserting new
columns
"Duration 1", then using using tools have gone to the
customize
fields window
and selected for summary tasks select Sum. The summary
task then
sums all of
the durations as calendar days. The problem is that some
of the
tasks are
concurrent. This gives me an inflated duration for the
summary
task. Any
ideas.

 

[Jeff Magaoitin]

Thank you Julie!!!
That was it exactly, for some reason it was defaulting to a 6 hour shift on
Sunday, when I finally got this corrected your calculation worked great!

Thanks for your help I have been pulling what little hair I have left out
over this one.

Have a great Day.

Jeff

 

[JulieS]

You're most welcome Jeff and thanks for the feedback. I'm glad all
worked out for you and you were able to keep your hair
Julie

 

[Paul Billings]

"Paul Billings"  wrote in message




Hello Paul,

I'm not sure I follow you completely.  True, Work = Duration *
Assignment Units, but you shouldn't have resource assigned to
summary tasks, so assignment units doesn't play into this.

You can certainly see a difference between durations on subtasks
versus duration on summary tasks due to differences in calendars
used to define the "working" time used in Duration.  For example:

[...]

Julie,

True, no resources should be assigned to summary tasks.

I've had clients become VERY confused when Duration, Start, and Finish
are shown. For a concrete task, as you know, Duration is always
directly related to the work through D=W*U. Duration is NOT the
number of working days between Start and Finish for a concrete task --
introduce a split to illustrate this. OK, fine. On the other hand, a
summary task duration is always the number of working days between
Start and Finish -- regardless of whether work is actually being done
on those days. (The pedantic case is a single concrete task under a
summary task with a split.)

I can accept two different definitions. However, for summary tasks,
telling someone the duration corresponds to "working days" is often
misunderstood. People normally equate this to "days worked". I've
just found it easier for people to accept two definitions that are a
bit more dissimilar when using calendar days for summary durations.

Paul

 

[JulieS]

"Paul Billings" wrote in message
<snip>
Julie,

True, no resources should be assigned to summary tasks.

I've had clients become VERY confused when Duration, Start, and
Finish
are shown. For a concrete task, as you know, Duration is always
directly related to the work through D=W*U. Duration is NOT the
number of working days between Start and Finish for a concrete
task --
introduce a split to illustrate this. OK, fine. On the other hand,
a
summary task duration is always the number of working days between
Start and Finish -- regardless of whether work is actually being
done
on those days. (The pedantic case is a single concrete task under a
summary task with a split.)

I can accept two different definitions. However, for summary tasks,
telling someone the duration corresponds to "working days" is often
misunderstood. People normally equate this to "days worked". I've
just found it easier for people to accept two definitions that are a
bit more dissimilar when using calendar days for summary durations.

Paul
------------------------------

I think we're on the same page here Paul I find it helpful to
add the comment "working days as defined on the project calendar"
when explaining the concept.
Julie

 

[PRibeiro]

Jeff:
I got the same exact problem. My "Calendar Days" duration also showe
up with partial days' durations, even if I have a calendar with a norma
7 days calendar 8.00-17.00 with 1 hour lunch and all tasks have ful
working days.
In another thread started by me regarding the partial days' durations
I found out that if you have constraints like "start no earlier than
the duration sometimes comes with partial days. I am not sure if thi
helps in your case.
But in this case, when I tried to replicate the method suggested b
JulieS it showed up partial days, even if I don't have any constraint i
my tasks.

Also, I noticed that when I added this customized field, Microsof
Project changed the duration of my tasks, what is a little bit strange
since the calendar didn't change and the only thing that I did was t
add the customized filed, which shouldn't have impact in the othe
"duration field".

Any clues

 

[JulieS]

Hello PRibeiro,

My comments are inline below.

Jeff:
I got the same exact problem. My "Calendar Days" duration also
showed
up with partial days' durations, even if I have a calendar with a
normal
7 days calendar 8.00-17.00 with 1 hour lunch and all tasks have
full
working days.

[Julie] Do you have resources assigned to the tasks? Are the
resource(s) calendars also set as 7 days per week, 8 hours per day?

In another thread started by me regarding the partial days'
durations,
I found out that if you have constraints like "start no earlier
than"
the duration sometimes comes with partial days. I am not sure if
this
helps in your case.
But in this case, when I tried to replicate the method suggested
by
JulieS it showed up partial days, even if I don't have any
constraint in
my tasks.

[Julie] Did you change the display of dates to show times as well
as dates? Again, as was true with Jeff, he had tasks which did not
span the full "day" on Sunday, causing start and finish times which
did not correspond to 08:00 nor 17:00.

Also, I noticed that when I added this customized field, Microsoft
Project changed the duration of my tasks, what is a little bit
strange,
since the calendar didn't change and the only thing that I did was
to
add the customized filed, which shouldn't have impact in the other
"duration field".

[Julie] A custom field should not be changing the calculated
duration if all you did was add the field. Did you change calendars
on the task?

Any clues?

[Julie] What release (2003? 2007?) of Project and what service pack
do you have applied?

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

 

[PRibeiro]

Hi Julie:
Thanks for your feedback. Please check my replies below.

Hello PRibeiro,

My comments are inline below.

Jeff:
I got the same exact problem. My "Calendar Days" duration also
showed
up with partial days' durations, even if I have a calendar with a
normal
7 days calendar 8.00-17.00 with 1 hour lunch and all tasks have
full
working days.

[Julie] Do you have resources assigned to the tasks? Are the
resource(s) calendars also set as 7 days per week, 8 hours per day?


[PRibeiro] No, I didn't assign any resources assigned in order t
reduce the number of fileds where the problem might be

In another thread started by me regarding the partial days'
durations,
I found out that if you have constraints like "start no earlier
than"
the duration sometimes comes with partial days. I am not sure if
this
helps in your case.
But in this case, when I tried to replicate the method suggested
by
JulieS it showed up partial days, even if I don't have any
constraint in
my tasks.

[Julie] Did you change the display of dates to show times as well
as dates? Again, as was true with Jeff, he had tasks which did not
span the full "day" on Sunday, causing start and finish times which
did not correspond to 08:00 nor 17:00.


[Pribeiro] In my original calendar, Sunday is a day-off, so no task
there. What I wanted is the same as Jeff. Since hte duration i
calculated in actual work days and my Sundays are day-off, this mean
that in the end the calendar days are more than the actual workin
days.Furthermore, all my tasks are full working days

Also, I noticed that when I added this customized field, Microsoft
Project changed the duration of my tasks, what is a little bit
strange,
since the calendar didn't change and the only thing that I did was
to
add the customized filed, which shouldn't have impact in the other
"duration field".

[Julie] A custom field should not be changing the calculated
duration if all you did was add the field. Did you change calendars
on the task?

[Pribeiro] No. My calendar remains with Sundays off.

Any clues?

[Julie] What release (2003? 2007?) of Project and what service pack
do you have applied?


[Pribeiro] Project 2007 SP1