I am seeing an issue where it appears that one repeating appointment is
masking another. This scenario is only happening on the T3 and TE
devices though. I am not seeing it on the Treo650 or on native 68K
devices. Here is the scenario:
I have two repeating appts that do not overlap. One starts 02/25/05 and
the other is 10/04/04. I am receiving these in a packet from a server.
I am writing these appointments to the classic calendar db. If I write
the 02/25/05 appt then the 10/04/04 one, I only see the 10/04/04 appt.
If I delete the 10/04/04 then the other shows up in the calendar. If I
write the 10/04/04 first then, both show up.
So I am wondering:
1. Is the order I write repeating appointments in important? If so why
is it only on these devices?
2. Is there a PACE layer issue I am not aware of?
3. Are there any known issues along these lines in managing the classic
calendar db and the newer db format?
I belive I can make it work by sorting repeating appts based on their
start date. However I never feel very warm and fuzzy about fixes that
seem work without understanding why. Any help would be much
appreciated.
Thanks,
Aaron Hansen
Extended Systems
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/support/forums/
