Rob,
It sounds like you intrepreted Ed's posting incorrectly. A combobox will cause the point to be moved in the rowsource table/cursor--which is not the table you want to actually modify. Be very careful that the controlsource is bound to a field in the table you are trying modify.

You do not need to do anything at all relating to selecting areas, or setting the relation between the master table and the lookup table. The cbo will do that for you.

>I think you hit the nail on the head concerning moving the record pointer in the master table -- but IMHO this sure seems like a VFP bug if true... What I'm choking on is that there is no relation set between the master table and the picklist used by the combobox field...
>
>I'll try to use the picklist as a cursor, and see if that solves the problem -- but I'm not confident, as it seems the same problem will happen...
>
>Thanx for the info. I'll post my results when I can get back out of the managerial/red-tape mess I've gotten into since this morning...
>
>Rob
>
>>
>>I don't know what you're actually doing with combo, but there are some things which might help you. When you drop combo and move through list portion items, you actually move record pointer in combo.rowsource, and it may harm other parts of your application/form which may use the same work area/alias, especially if you use bound controls and/or temp relationships. The safer method is to populate combo either from cursor or even using AddItem (if you have few items).