Thank you all for the suggestions.
--
David Thacker
http://www.SatelliteForms.net
The Premier RAD Tool for PalmOS PocketPC
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
My app handles large databases, sometimes with as many as 32,000 records, and
NVFS is a major headache for me.
NVFS is not the only thing that affects performance. Another important factor
is the memory speed. Some models, such as the Tungsten T, have relatively slow
memory, and perform badly
, 2007 3:13 AM
To: Palm Developer Forum
Subject: Re: Significant performance problem using QuickSort on newer NVFS
implementations?
My app handles large databases, sometimes with as many as 32,000 records,
and NVFS is a major headache for me.
NVFS is not the only thing that affects performance
Can anyone from Access/PalmSource and/or Palm Inc. comment on these NVFS
quicksort performance results? Is this problem going to be fixed in the
next NVFS revision, are there suggestions to improve sorting performance
other than use less records, etc.?
Ben Combee? Greg Wilson?
I don't know
Ben Combee wrote in message news:[EMAIL PROTECTED]
Can anyone from Access/PalmSource and/or Palm Inc. comment on these NVFS
quicksort performance results? Is this problem going to be fixed in the
next NVFS revision, are there suggestions to improve sorting performance
other than use less
I guess the best solution right now will be to simply duplicate those
multi-megabyte databases with different sort orders, so that QuickSort does
not have to be called on the handheld. The added storage requirements of
that solution are definitely easier to swallow than the painful sort
How large are the database records?
One thing you might try is just to follow the advice to create an array of
indexes, sort it with SysQuickSort(), and then you could write out the database
manually in the specified order, as long as you can count on having the space
for two copies of the
