NewDeal Hot Tip 1700PIMs
If you change the setting in this option, it will be applied to all new events you enter. It will not affect any existing alarmed events.
Example: It is 1:00 pm. You enter an alarmed event for 3:00 pm with the default settings. This means the alarm will activate at 3:00 pm. At 1:30 pm, you decide that you better be reminded about the 3:00 pm at 2:30, so you go into Options, Reminder Precedes Event by... and change the time from 0 to 30 minutes. Result: Alarm fails to go off at 2:30 pm. It will go off at 3:00 pm. Reason: The settings in Options do not affect previously set alarms. In this case, the change in alarm time should be made in Edit, Alarm Settings.
Time progression conflicts
You've set the global default for alarm activation in Options, Reminder Precedes Event By... to 30 minutes and you've saved this configuration for future use. You go into NewPlanner and enter an alarmed event. Result: the alarm does not go off at the you expected it to activate. Reason: The alarm time you set falls outside the parameters of the global alarm time default you set.
Example: You have your global alarm time set for 30 minutes. This means that all alarmed events you now enter will activate 30 minutes before event time. It's 2:00 pm. You enter an event for 2:15 pm and continue working in GEOS. At 2:15 pm, the alarm fails to activate.
What happened? If you select the event and choose Edit, Alarm Settings, you'll see that the alarm was not set to activate at 2:15 pm, but at 1:45 pm, 30 minutes before the event... just as your self-set global default specified. Since you only entered the event at 2:00 pm, you missed your own 30 minute threshold by 15 minutes. The setting for this event in Edit, Alarm Settings reads, as it should, 1:45 pm. As far as NewPlanner is concerned, the alarm already went off.
Remember your global alarm setting in Options, or at least check new events in Edit, Alarm Settings to be sure you don't run into this time progression conflict.
Last Modified 6 Mar 1999