Here's an idea: See if the modificationNumber returned by DmDatabaseInfo has
changed. I haven't tried this, but I think it should work, with some
caveats.
Most Data Manager functions that modify the contents of a database bump the
modification number of the database, but not all. For example, you can use
DmQueryRecord to get a handle to a record, lock the handle, and DmWrite to
the record, all without incrementing the modification number. This is, of
course, bad policy - you're supposed to use DmGetRecord and DmReleaseRecord
if you're going to modify the record. The app info block can also be
modified without affecting the modification number.
So have a look at the source code for the Address app and the Data Manager
to make sure this isn't happening, or at least isn't happening in cases that
you care about.
I assume that the modification number gets bumped when the database is
updated during a HotSync, but I'd verify this too.
Has anyone tried this approach?
--
Danny
"Ng Wei Gee" <[EMAIL PROTECTED]> wrote in message
news:48666@palm-dev-forum...
> Hi all,
>
> I would like to write an app that reads the database from the Address app
> and display the data. I would like to generate some indices based on the
> database so that sorting could be done based on different criterion. In
> order to speed up the app, I would like to store these indices in a
database
> so that they need not be generated (takes a long time on large databases!)
> on every run. Instead, they should be re-generated only if the address app
> changed some records (delete/insert/edit/etc). I would like to ask if
anyone
> has any pointers on this issue. Thanks in advance!
>
> Regards,
> Gee.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
