Oh, PalmOS 3.3... this is probably a sort-of-bug.
You'll get it under certain circumstances when setting the time from a
background thread.
Probably the only way around it is to not set the time from that launchcode...
instead, try this: Set an alarm for a few seconds later, and then wait for it
to go off.
When your app is called with the alarm launchcode, set the time.
Jesse
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html