You could create a cursor (at the beginning of the "edit session") that has a one-to-one relation into the customer; eg.

cursor->customer->>ticklers

Instead of navigating the "customer" directly, you would navigate it via the cursor (the cursor being sorted in the desired "tickler date" order).

Any changes to the customer tickler dates (in this session) would not effect the "viewing order" (until the next session).

>My app has a page for customer and a page for ticklers. The customer page shows detail for a single customer. The tickler page has a grid that shows the ticklers for a single customer. The toolbar has NEXT, PREV, TOP, BOT, and SORT buttons.
>
>Each tickler row has a start_dt and compl_dt. My client wants to sort the customers to start at the first customer with an over due tickler and then NEXT to the next customer with an over due tickler so that he can work them - start_dt < date() and empty(complete_dt). I have put the appropriate index on the customer table since that table is the navigational table for the tickler table, and when you NEXT it advances the customer table, seeks on the tickler table, and then builds the tickler grid. This index works for both the customer and tickle page. The customer start_dt is maintained everytime a tickler start_dt is updated (all ticklers for a customer are read and the ticler.start_dt that is smallest with an empty(compl_date) is saved to the customer record).
>
>Problem is that when the client works an overdue tickle he might change the start_dt or compl_dt. By changing the start_dt the current customer changes position in the indexed customer table. So NEXT will not take them to the next tickler that is overdue.
>
>It is easy to understand what the customer wants, but I am having a difficult time knowing how to program it. Any help is appreciated. Hope the above makes sense.
>
>Thanks
>
>Brenda