>Hm. I like cbo's to use a SQL-Select or AddItem rowsource so that record pointer changes in the cbo's rowsource don't impact the record pointer for the other (textbox) controls.

Well, now your talking about me wrestling with yet again more new territory, when, in theory, what I've got ought to work for me. I've got to finish my project in finite time so, although I've played around a little with SQL-Select, I'd like to avoid Micky Mouse's faux-pas with the broomsticks when he messed around with too much magic. And I think you have to admit. With SQL were talking serious magic.

Secondly, I'm using the primary combolist to select the row of interest in the table so it seems like having it's cbo rowsource impact the record pointer is EXACTLY what I want (he said, questioningly)

>
>>I notice that the interactivechange event does not fire when I use an ENTER

>Do you mean you issue a KEYBOARD? Then, yes, the programmatic change is fired. You can simply put a call to the interactivechange() method in the programmaticchange method.

Since I don't know what you mean by 'issue a KEYBOARD' I don't think I do. I used the debug events tracer to see what happens when I hit the ENTER key when the focus is on the cbo's textbox. interactivechange does not appear to be firing in this case. (Though the extra gobbledygook that's traced when I switch between my form and the debugger window could be confusing me)