Yes. I first noticed that after I'd set some look-up FKs from listboxes, on the INFOBASE rec (textbox shows the key and listbox shows the look-up text name), and saved, the values disappeared from the record. These are chronological journey records pertaining to a parent ROUTE. There may be many of them for each Route, all maybe practically identical save for their start and end times, so I'd not noticed the rec changing in the past (if it did).

So when I checked the list page of the form I found that i'd gone to eof(). Recs near the bottom of the table had got the values I'd just edited in. I thought I'd found the flaw in my class save logic and fixed this. Further tracing found this command was the culprit.

>Does it happen if you don't have Browse open?
>
>>UPDATE: I can confirm that this line of code does not fire a trigger :-?
>>
>>>Do you have a trigger on the table?
>>>
>>>>Hi Sergey. Thanks
>>>>
>>>>No it's a well-established database table
>>>>There is no timer in operation
>>>>
>>>>>Is it a free table? Do you have a timer that could move pointer?
>>>>>