|
#1
|
|||
|
|||
Problem with begin date
I am using Appointments to record birthdays.
i) I set the Begin Date to the persons birthday. ii) I set recurring to 1 year. iii) I set reminder to 0 minutes. iv) I get a reminder (because was event create in the past) v) The Original Begin date is automatically set. vi) The new Begin Date is automatically set. The problem I am seeing is that occasionally the new begin date is being set incorrectly. For example in step i I set Begin Date to 12/09/1992, once the first reminder is dismissed the new Begin Date is set to 13/09/2006 not 12/09/2006 as expected. Note that this appears only to occur with some dates. What am I doing wrong? |
#2
|
|||
|
|||
Your report identified a bug related to leap year computations when advancing a Yearly Recurring Reminder. It only comes into play when advancing from a Leap Year (with a Begin Date of March or later).
The workaround for now is to simply not add Yearly Recurring Reminder Begin Date values in the distant past (simply enter them for this year or last year). This will always avoid the bug since this year (or last year) is not a Leap Year. Entering a more distant Begin Date will immediately advance to the next recurrence when initially dismissed anyway... The bug will be addressed in the next release. |
#3
|
|||
|
|||
Thanks :-)
|
|
|