Andy, >I would >add that a full (bidirectional) sync will tend to go faster since you are >probably making only a few changes to the database, versus uploading them >all every time.
I think this is still going to be application dependent. For example, I have inventory databases which can easily exceed well over 30,000 products, and which contain highly volitile information such as quantity available, estimates ship dates, etc. I'm only aware of clients with around 50k products loaded, but my paradigm is not limited to 64k. It will take as many products as you can fit in storage. At any given client, there may be any number of devices to be synced on whatever frequency they want, typically daily. They may not do every one every time, depending on the expected volume and number of employees working that day. The devices may also get synced at any of multiple locations (cradles) -- depending on which one happens to be available or convenient at the time. Hot Sync reverts to a slower mode when a handheld syncs at multiple PCs. In my experience in this scenario, it is MUCH faster to just completely replace the database each time using record lengths close to 64K. It also allows me to include my own "indexes" over the products so I can instantly locate any product by SKU or bar code or description or vendor or ... Transfer time is thus based solely on volume and connection type, not number of records. With literally hundreds of products contained in one physical PDB record, and with inventory quantities tracked per product, it is more efficient to just forget about dirty flags and replace the database en masse. YMMV Doug -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
