Ah the linked list approach...thought of that...but then I'd have to rewrite all the API's to use my linked list instead of just using the standard NextRecordXXX etc.
But, then...which is better? If I used the linked list approach, I could maintain multiple sorts on the database....hmmm.. interesting idea... Hard call... James Mitch Fawcett wrote: >I seem to recall having a similar problem a couple of years back when I >wanted to keep my data in a physically sorted order. The way I made sure >that an edited record had a certain Index number was to use DmDetachRecord >to take the record being edited out of the database, edit it, and then use >DmAttachRecord to insert it back in. DmAttachRecord's 2nd parameter >specifies the index position. > >If I had to do it again I would use a linked list approach instead of >keeping my data physically sorted. > >Mitch Fawcett >Tapn'see Software >www.tapnsee.com >Home of SuperList3 > >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED]]On Behalf Of James >>Barwick >>Sent: Friday, December 28, 2001 6:06 PM >>To: Palm Developer Forum >>Subject: Insert in order problem - Database Inserts and Categories >> >> >>OK Palm Guru's....please tell me how to insert in order....here's the >>problem. >> >>Record Index Value Category >>0 A 1 >>1 B 1 >>2 C 1 >>3 D 2 >>4 E 2 >>5 F 2 >> >>When I display records in a list and display category 2 I get the >>following >> >>Record Index Value Category >> > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
