>A normalized table would completely remove this problem.
>
>One good piece of advice I learned years ago was: "When you start creating fields with numbers to show their order, you're making a mistake."

"Repeater Groups" if my memory serves me well ?!

I've just had to totally restructure my system, of Bus Stops in Routes, from a legacy table structure, where there were a max. of 110 stops per route, stored in the Journeys table as Stop1-Time1, Stop2-Time2, ... Stop110. One of these recs for each sequence of the route (i.e. for each indiv. start time). Many routes only have, say, <= 70 stops, so most of the fields were wasted anyway. On top of this, each route had an accompanying 1-1 rec, giving each of 110 stops and what zones they pass through.

It had been guaranteed in the past that there would never be more than 110 stops and, despite my protest that normalisation was the key, I was told to follow the old structure. So the whole system was built on this. Next I have to write an import program, then find several routes with 135 or more stops in.

DAN - DAN - DAAAAAAAN!