An application I'm developing requires a pre-generated database with lots of tiny read-only records. Obviously, this is going to be problematical with NVFS, so I decided to pack multiple records into a single record, and use a sortinfo block to keep a map logical records to physical records.
Unfortunately, when I hotsync this database to a device, the sortinfo block gets lost - it's gone on the handheld's database. For laughs, I used drivemode to copy the database into the expansion card, then I used Filez to copy it to main memory (presumably via VFSImportDatabaseFromFile()). Lo and behold, the sortinfo block survived intact. I then did a hotsync in order to get the database back onto the desktop via the backup conduit. Dumping the database showed that the sortinfo block was still intact. So then I deleted the databases from the handheld, and re-installed them using the database files that were created by the backup conduit. The sortinfo block was lost. So, it appears that installing databases to the device via the hotsync protocol will not preserve the sortinfo block. It does not appear to be a problem with the Hotsync Manager - using pilot-link's pilot-xfer program had the same results. It also does not appear to be a problem with the T5 - I got the same results when syncing to an old Clie running PalmOS 4.x. It also seems to affect POSE when you drag files to it, but it does not affect the T5 simulator. I doubt that there's any solution to this; I just felt like whinging about how my first ever solution that actually uses a sortinfo block appears to have been stillborn. -- Dave Carrigan Seattle, WA, USA [EMAIL PROTECTED] | http://www.rudedog.org/ | ICQ:161669680 UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-C++-DNS-PalmOS-PostgreSQL-MySQL -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
