I would just consider this to be a bug. Entering a start date that is 9 months ahead of today is not logical as a default entry.
The app should understand that all short dates are for the current year ONLY if that would be a date of today or later. For example, a short date of 12/12 should be understood as Dec 12, 2010. However, a short date earlier than today, say 2/12, should be for the following year (2/12/2011). Having it be 2/12/2010 is not logical. People should be forced to enter dates in a long format for dates earlier than today for for dates more than 1 year out (e.g. 2/12/2012). That is easy enought to put into their routine when it converts a short date to a long date on your behalf. On Nov 2, 2:58 pm, Mike T <[email protected]> wrote: > Now that its late in the year, I find myself entering tasks that I > know I won't start until next year. But if I'm entering the start > date as 2/1 and then hit <CR> the date that gets filled in is > 2/1/2010. I looked in the archives here and couldn't find any way to > configure MLO so that if you don't enter a year the default value is > for next year, not this year. > > Does anybody know how to configure MLO so that the year for a > partially entered date is in the future, not the past? Or would this > require a change to the software? -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en.
