Newbie - Enter "normal" task durations: 30-day 45-day etc
in [Project]
|
From: Michael T on 12 Jan 2010 10:55 Sai wrote: > On Jan 12, 9:40 am, Michael T <chilledmonkeybrains...(a)gmail.com> > wrote: > >>Many eons ago using an early version of Project, I could enter tasks of 30, 45, >>60, 75 days, etc., duration to mean a month, month-and-a-half, etc., and the >>program understood I meant for these time blocks to span non-working days >>(weekends); so for example, a "30-day" task entered on May 1 would finish June 1. >> >>Fast-forward to the present day, and my Project 2007 interprets "30 days" to >>mean 30 *work* days rather than 30 calendar days. >> >>How can I use 30/45/60/75 etc., again and get the durations I used to? A few >>googlings hinted this'd be a setting in Tools> Options, but nothing there jumps >>out. >> >>Grateful for any clues or pointers to a good newbie FAQ. >> >>Michael > > > Michael - > > To enter calendar days, you need go for elapsed days. Elapsed days > ignores the distinction between working and non working time on > calendars. So, instead of entering 30 days, type 30 edays. > > Refer: http://alturl.com/wcg5 > > Please let us know if this helps > > - Sai, PMP, PMI-SP, MCTS, MCT > http://saipower.wordpress.com Sai - That works beautifully, I really appreciate the tip! Pity I don't see 'edays' documented anywhere. Trevor and spamboy - Thanks for the elaboration, but I think you may idealize the typical frantic office and the trainability of the annointed ones. My bosses would return only belly-laughs if I suggested they modify the 30/45/60/etc concepts that they toss around so freely and frequently. Michael
From: Michael T on 12 Jan 2010 14:05 Sai wrote: > On Jan 12, 9:40 am, Michael T <chilledmonkeybrains...(a)gmail.com> > wrote: > >>Many eons ago using an early version of Project, I could enter tasks of 30, 45, >>60, 75 days, etc., duration to mean a month, month-and-a-half, etc., and the >>program understood I meant for these time blocks to span non-working days >>(weekends); so for example, a "30-day" task entered on May 1 would finish June 1. >> >>Fast-forward to the present day, and my Project 2007 interprets "30 days" to >>mean 30 *work* days rather than 30 calendar days. >> >>How can I use 30/45/60/75 etc., again and get the durations I used to? A few >>googlings hinted this'd be a setting in Tools> Options, but nothing there jumps >>out. >> >>Grateful for any clues or pointers to a good newbie FAQ. >> >>Michael > > > Michael - > > To enter calendar days, you need go for elapsed days. Elapsed days > ignores the distinction between working and non working time on > calendars. So, instead of entering 30 days, type 30 edays. > > Refer: http://alturl.com/wcg5 > > Please let us know if this helps > > - Sai, PMP, PMI-SP, MCTS, MCT > http://saipower.wordpress.com Sai - Is there any way to make the duration column *say* days but mean edays? (Boss points out 'edays' is not exactly user friendly....) TIA Michael
From: Rob Schneider on 12 Jan 2010 14:37 No. I had a boss like that once. Solution was to keep her/him (I'm not say which) as far away as possible from the project. Things went prety well after that. :-) --rms www.rmschneider.com On 12/01/10 19:05, Michael T wrote: > > > Sai wrote: >> On Jan 12, 9:40 am, Michael T <chilledmonkeybrains...(a)gmail.com> >> wrote: >> >>> Many eons ago using an early version of Project, I could enter tasks >>> of 30, 45, >>> 60, 75 days, etc., duration to mean a month, month-and-a-half, etc., >>> and the >>> program understood I meant for these time blocks to span non-working >>> days >>> (weekends); so for example, a "30-day" task entered on May 1 would >>> finish June 1. >>> >>> Fast-forward to the present day, and my Project 2007 interprets "30 >>> days" to >>> mean 30 *work* days rather than 30 calendar days. >>> >>> How can I use 30/45/60/75 etc., again and get the durations I used >>> to? A few >>> googlings hinted this'd be a setting in Tools> Options, but nothing >>> there jumps >>> out. >>> >>> Grateful for any clues or pointers to a good newbie FAQ. >>> >>> Michael >> >> >> Michael - >> >> To enter calendar days, you need go for elapsed days. Elapsed days >> ignores the distinction between working and non working time on >> calendars. So, instead of entering 30 days, type 30 edays. >> >> Refer: http://alturl.com/wcg5 >> >> Please let us know if this helps >> >> - Sai, PMP, PMI-SP, MCTS, MCT >> http://saipower.wordpress.com > > Sai - Is there any way to make the duration column *say* days but mean > edays? (Boss points out 'edays' is not exactly user friendly....) > > TIA > Michael
From: Trevor Rabey on 13 Jan 2010 01:02 I am not responsible for your boss's attitudes, misconceptions and erroneous notions, and since they have no consequences that I have to live with I am not very concerned about them. I am well aware of the imperfect and un-ideal state of reality. We have been seeing weird, half-baked and ineffective ideas in this newsgroup for the past 10 - 15 years, and also commonplace in the "real world", so it is no surprise. Who laffs at who? If they did a bit or research and reading they would learn something. Are you sure it isn't a case of they don't know what they don't know? But, hey, if their projects work and they are satisfied with the results they should carry on. Right or wrong, everyone is free to do it their own way. -- Trevor Rabey 0407213955 61 8 92727485 PERFECT PROJECT PLANNING www.perfectproject.com.au "Michael T" <chilledmonkeybrains100(a)gmail.com> wrote in message news:eAPy5%235kKHA.2188(a)TK2MSFTNGP04.phx.gbl... > > Sai wrote: >> On Jan 12, 9:40 am, Michael T <chilledmonkeybrains...(a)gmail.com> >> wrote: >> >>>Many eons ago using an early version of Project, I could enter tasks of >>>30, 45, >>>60, 75 days, etc., duration to mean a month, month-and-a-half, etc., and >>>the >>>program understood I meant for these time blocks to span non-working days >>>(weekends); so for example, a "30-day" task entered on May 1 would finish >>>June 1. >>> >>>Fast-forward to the present day, and my Project 2007 interprets "30 days" >>>to >>>mean 30 *work* days rather than 30 calendar days. >>> >>>How can I use 30/45/60/75 etc., again and get the durations I used to? A >>>few >>>googlings hinted this'd be a setting in Tools> Options, but nothing there >>>jumps >>>out. >>> >>>Grateful for any clues or pointers to a good newbie FAQ. >>> >>>Michael >> >> >> Michael - >> >> To enter calendar days, you need go for elapsed days. Elapsed days >> ignores the distinction between working and non working time on >> calendars. So, instead of entering 30 days, type 30 edays. >> >> Refer: http://alturl.com/wcg5 >> >> Please let us know if this helps >> >> - Sai, PMP, PMI-SP, MCTS, MCT >> http://saipower.wordpress.com > > Sai - That works beautifully, I really appreciate the tip! Pity I don't > see 'edays' documented anywhere. > > Trevor and spamboy - Thanks for the elaboration, but I think you may > idealize the typical frantic office and the trainability of the annointed > ones. My bosses would return only belly-laughs if I suggested they modify > the 30/45/60/etc > concepts that they toss around so freely and frequently. > > Michael >
From: Sai on 15 Jan 2010 06:46 On Jan 13, 12:05 am, Michael T <chilledmonkeybrains...(a)gmail.com> wrote: > Sai wrote: > > On Jan 12, 9:40 am, Michael T <chilledmonkeybrains...(a)gmail.com> > > wrote: > > >>Many eons ago using an early version of Project, I could enter tasks of 30, 45, > >>60, 75 days, etc., duration to mean a month, month-and-a-half, etc., and the > >>program understood I meant for these time blocks to span non-working days > >>(weekends); so for example, a "30-day" task entered on May 1 would finish June 1. > > >>Fast-forward to the present day, and my Project 2007 interprets "30 days" to > >>mean 30 *work* days rather than 30 calendar days. > > >>How can I use 30/45/60/75 etc., again and get the durations I used to? A few > >>googlings hinted this'd be a setting in Tools> Options, but nothing there jumps > >>out. > > >>Grateful for any clues or pointers to a good newbie FAQ. > > >>Michael > > > Michael - > > > To enter calendar days, you need go for elapsed days. Elapsed days > > ignores the distinction between working and non working time on > > calendars. So, instead of entering 30 days, type 30 edays. > > > Refer:http://alturl.com/wcg5 > > > Please let us know if this helps > > > - Sai, PMP, PMI-SP, MCTS, MCT > >http://saipower.wordpress.com > > Sai - Is there any way to make the duration column *say* days but mean edays? > (Boss points out 'edays' is not exactly user friendly....) > > TIA > Michael- Hide quoted text - > > - Show quoted text - No. Sorry, you need to indicate somewhere it is calendar days and so edays is MUST :-) - Sai
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: Date 1 field not updating automatically Next: Planned vs Actual Percentage Completed |