>>Spare me hunting down the rest of the thread - what's the key expression for the current tag? Could it be that it's somehow empty for other records and filled for the current - so it jumps to the bottom (bottom or eof() - the difference makes a difference).
>
>rte_no + rte_let + directn + var_code +days_op + j_start
>
>route # + geeration ("A"-"Z") + direction ("O"/"R") + variant ("A"-"Z") + Days. operating + Journey start time {char(4) - "0000" - "2359"}

It really doesn't seem like the days_op is a significant influence on the key value...

>Now if the days_op changed then the rec MIGHT want to be in a different position, but surely not till all saved. But it isn't.

...ah, but why would Fox care about displaying the data on disk and neglect to display the data on your machine? IMO, it would display them in proper order right away, flushed or not. Simple way to test: get your days_op="-------" and try again. Did the record jump to its previous position?