I implemented lookup tables so that I can sort my records in multiple orders without changing the record indexes. I needed to do this because I have relational data that stores the actual record index as a *unique ID*. Ofcourse, I have to handle adding, inserting, and deleting myself.
It runs great on my m515 and fixed a problem in my owner draw list where I was displaying text from a record that was being "looked up" by DmFindRecordByID() and was causing the display to be very choppy when scrolling. The records get looked up lightning fast now (actually O(log n) time). I would recommend Henk's idea if you are really looking for performance. Brad "Henk Jonas" <[EMAIL PROTECTED]> wrote in message news:97029@palm-dev-forum... > > I did, I stored the unique IDs for 3 different sortings, but I figured > out that it was slower to use them than a standart QuickSort. Maybe it > would be better not to sort at all, but have a sorted list of indexes as > a kind of lookup table. > > Henk > > Ron Clabo wrote: > > > Seems like this my be a seldom used aspect of the palm database > > architecture. Anyone using the sort info block to boost search performance? > > Any tips? > > > > -Ron > > > > > > > > > > > > > -- > ------------------------------------------------------------------------- > [EMAIL PROTECTED] www.metaviewsoft.de > > <A HREF="http://www.handango.com/PlatformTopSoftware.jsp?authorId=95946";> > <IMG SRC="http://user.cs.tu-berlin.de/~jonash/werbung.jpg";></A> > ------------------------------------------------------------------------- > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
![http://user.cs.tu-berlin.de/~jonash/werbung.jpg"](http://user.cs.tu-berlin.de/~jonash/werbung.jpg"){kind=link}