Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Question emon 1
- Thread starter kaney
- Start date
-
1
- #2
mon = month
emon = elapsed month
Month is defined in Tools | Options | Calendar-tab.
Setting "month" to 20 days (the default) means that two tasks in an FS link with a 1mon lag will occur 20 days apart. But these lags can be affected by a change in the duration of a month -- which we'll see in a moment.
Elapsed Month is a 30 day month. This is a fixed number.
You can get a good idea of what this means by creating pairs of milestone (0d work; 0d duration) tasks T1A, T1B and T2A, T2B and linking them with a standard FS link. Change the Link on T1A-T1B to a lag of 1mon and change the Link on T2A-T2B to a lage of 1emon.
Now, set the start dates for T1A and T2A to (and I chose these dates specifically so that the month begins on a Monday, the 1st).
1. Feb 1, 2010 (a 28-day month)
2. Jun 1, 2009 (a 30-day month)
3. Dec 1, 2008 (a 31-day month)
Look at the Start Dates for T1B and T2B. That's the difference between "mon" and "emon".
Now try this:
Tools | Options | Calendar-tab and change the "month" value from its default (20) to 25. Notice how Project has preserved the lag but changed the units in the lag for those task lags that used the "mon" unit but made no change to the task lags where the "emon" unit was used.
Yes, there are also eday, ewk to accompany emon - but there is no eyr.
The keen student will want to repeat the above experiments using 1wk and 1ewk to see what happens.
emon = elapsed month
Month is defined in Tools | Options | Calendar-tab.
Setting "month" to 20 days (the default) means that two tasks in an FS link with a 1mon lag will occur 20 days apart. But these lags can be affected by a change in the duration of a month -- which we'll see in a moment.
Elapsed Month is a 30 day month. This is a fixed number.
You can get a good idea of what this means by creating pairs of milestone (0d work; 0d duration) tasks T1A, T1B and T2A, T2B and linking them with a standard FS link. Change the Link on T1A-T1B to a lag of 1mon and change the Link on T2A-T2B to a lage of 1emon.
Now, set the start dates for T1A and T2A to (and I chose these dates specifically so that the month begins on a Monday, the 1st).
1. Feb 1, 2010 (a 28-day month)
2. Jun 1, 2009 (a 30-day month)
3. Dec 1, 2008 (a 31-day month)
Look at the Start Dates for T1B and T2B. That's the difference between "mon" and "emon".
Now try this:
Tools | Options | Calendar-tab and change the "month" value from its default (20) to 25. Notice how Project has preserved the lag but changed the units in the lag for those task lags that used the "mon" unit but made no change to the task lags where the "emon" unit was used.
Yes, there are also eday, ewk to accompany emon - but there is no eyr.
The keen student will want to repeat the above experiments using 1wk and 1ewk to see what happens.
- Status
Similar threads
- Locked
- Question