>>>But that should just get your record to be the last record (assuming you're entering a date larger than any other), not EOF(). Try with an older date - i.e. not today, but a date less than the latest date in the table, that should set your record as not the last.
>>
>>DAYS_Op is a 7 char field to denote what days the Journey runs, not a date, as I explained in another fork. If every day then it will hold "MTWTFSS". If the bus doesn't run, say, wed and thu then it will be "MT--FSS".
>
>Seems to be this one runs only mid-week, i.e. it's a "--WTF--" :).
lol
>
>
>>>BTW, are you sure it's eof("infobase")? Could it be something else (a related table, perhaps) is at eof()?
>>
>>I have the infobase up in a browse whilst tracing. As soon as the repl day-op is executed - ZAP - off to last rec.
>
>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"}
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.
- Whoever said that women are the weaker sex never tried to wrest the bedclothes off one in the middle of the night
- Worry is the interest you pay, in advance, for a loan that you may never need to take out.