Hello Jim, Unfortunately, there is no way around this for now. Perhaps PalmOne will issue a patch, but we don't have any news that one is coming as of yet. The minimum record size on the T5 is actually 512 bytes, which explains the bloat you are seeing. There are some user level documents which explain this fairly nicely: http://kb.palmone.com/SRVS/CGI-BIN/WEBCGI.EXE?New,Kb=PalmSupportKB,ts=Palm_External2001,case=obj(35222) http://kb.palmone.com/SRVS/CGI-BIN/WEBCGI.EXE?New,Kb=PalmSupportKB,ts=Palm_External2001,case=obj(34247)
And there is also the NVFS whitepaper, which you can find from the PalmOne Plugged-In program. (Search development resources, then set device to Any and resource type to White Paper) You can get around this problem though, and you don't have to reduce the number of actual records you have. What you will need to do is implement a logical record scheme where one physical record holds many logical records. Really, you just need to keep track of your record indexes and offsets differently: physicalIndex = logicalIndex / logicalRecordsPerPhysical; physicalOffset = logicalRecordSize * (logicalIndex % logicalRecordsPerPhysical); Of course, it would be a good idea to put this functionality in a wrapper class of some sort, so that you have a new "logical family" of database functions to perform all of your physical <-> logical translation for you. This might be a pain at first, but once it's done, you just call the logical family methods you make instead of the native Palm API. Besides getting rid of the database bloat, as an added bonus, your HotSync times will be dramatically reduced. I recently had to move to logical records myself and I almost couldn't believe how much faster the HotSync process became. Adrien. Tuesday, May 3, 2005, 4:43:18 AM, you wrote: JB> Mikhail Barashkov wrote: >> >>> I am building pdb files externally and am HotSyncing them onto the T5. >>> In doing so the pdb file size grows over 10x. The same pdb files >>> HotSync onto a T3 and older PDAs have no appreciable change in file >>> size. Yet even with the pdb file growth the palm applications can >>> still read the files without any sign of corruption, but the >>> application does run significantly slower then when the same >>> application and databases are run on a T3. >>> >>> Any ideas? >> >> >> Due to T5 memory organization, you lose an average of 256*n bytes on a >> database, where n is number of records. >> So the only solution is to decease num. of records in database. >> Mikhail Barashkov >> JB> Thanks Mikhail, JB> In my case the loss is linear as you suggested, but it is about 494 JB> bytes per record. Can it be really that bad? Is there anything other JB> then reducing the number of records that can be done? JB> Jim B -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
