I believe that each database has it's own "last
backed up" date.
When your app starts, it could compare the
backed-up date on the datebook db against
a date for the last datebook db backup that it
remembers privately.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
Robert McKenzie wrote in message <5585@palm-dev-forum>...
>
>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.
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
