I have an application that shares data with datebook.
This has given rise to many interesting problems in trying to
keep two different copies of the same data in sync.
Most of which I have overcome -- but not all.
In particular, the following problem has arisen:
- my application is installed on the palm.
- my conduit is not installed on the desktop
(say the user syncs at work & at home and
doesn't have our software at home).
- the user makes changes to his calendar in that
palm desktop and syncs, changing DatebookDB.
Note that DatebookDB's dirty bits will all be
clean at this point (datcn is a tidy little conduit).
I would like to be able to reliably detect this situation
on the palm, so that I can compare datebook's data and
mine and make the indicated changes on my side.
However, I do not get a sysAppLaunchCmdSyncNotify in
this situation, as my database has not (yet) changed!
I realize that DatebookDB's modification number will
have moved in this situation. However, it also moves
when the user modifies appointments on the Palm, and
I need to be able to tell the two situations apart.
(When the user modifies things on the Palm, the records are
left dirty; when the conduit does it, they are left
clean. In the former case I need only look at the
dirty records; in the latter, I must look at them all.
For performance reasons I do not want to look at them
all if I can avoid it.)
Ideas? Suggestions? (I have also already tried and
tried to convince management that we shouldn't duplicate
data, but to absolutely no avail.)
-bob mckenzie
<[EMAIL PROTECTED]>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
