>A cheesy solution is to store the ID value (or other determining value like Recno()) of the FOLLOWING record (Ford in this case). Make your change and then return to Ford.

I've implemented something like this but was hoping for something REALLY simple. The behavior I wanted to emulate was like the BROWSE window where changing an indexed field and pressing {DOWN} goes to the next visible record. The change to the index doesn't appear to take effect until the changed record leaves the visible browse window. I thought I had seen something about this, but couldn't remember exactly what, or where.
>
>Since you're changing the indexed field, you can also SET NEAR ON, seek the original value you change (SEEK 'Berra'). It will find the record AFTER Berra since Berra is now Pepitone.

I'm not sure this would work in all cases. If I changed 'Berra' to 'Boyer' and did a soft seek on 'Berra', wouldn't it now be pointing to 'Boyer'?


Thanks for you help..........Rich