Hi all. I'll apologize in advance for the size of this post... :\
I've developed my first app now for the PalmOS and had the non-release
version shown to our clients to their delight. (thank you to the entire
Palm Dev Forum
by the way for answering the rookiest of questions ;) )
The app is an aid to our Unix based Information Management System that
tracks -among
other things- product inventory in stores. The requirements are to be able
to store up to
100 bytes of information per record at up to 65,000 records.
What I'm currently doing is packing as many of our records (null delimited
and sorted alpha-
numerically) into each Palm record up to the 64k limit (give or take) and
creating an index
record as the the very last palm record which contains the very first
product number stored
in each previous palm record. When searching, I refer to this index record
to know what Palm
record to search in.
This is all fine and dandy so far, but now in terms of syncing, this
database structure is limited
in that if a product is deleted or added, chances are that every palm
record will need to be
re-syncd.
With this in mind, those above me are considering on lowering our max of
65,000 to 40,000 if
I can efficiently store, add, subtract, and index these items as an
individual palm record. The
idea is that the initial sync will take upwards of 8-15 hours. But syncing
the information, will be
minimal in this respect. What do you think of my current approach? What do
you think of the
alternative? How would you go about this project?
Thanks for taking the time to read this post. :)
Nole
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
