>>>>Yes, with rowsource of fields it was always so, even in DOS days IIRC. If that causes unwanted behavior, you can select the relevant fields into a separate cursor for that combo so that it doesn't affect an alias which you use elsewhere. If the records in that alias may change and you want the combo to reflect the change, well, requery it as needed.
>>>
>>>Thx. Can't believe it's been around as long as that without being fixed since it's obviously not an intuitive or expected behaviour. Also can't believe I hadn't been hit by it before.....
>>>Anyway I've got a workaround in place and can now get back to using IDEs that work as expected (g,d&r)
>>
>>You may want to recheck your expectations, I suspect the bug may be in there...
>
>Hmm. You think it is logical for the record pointer to move when the selected item in the combobox remains the same ?

Ouch... forgot that one. I thought it would settle on the selected item on .lostfocus()... I guess that's the reason the last time I had a combo on an alias used also in other places very very long ago. Come to think of it, all my combos use an array, and any synchronization with other data happens in .refresh(), which calls .requery(), or have values filled in .init() if the content is always the same. That was my way of taming the combo.