if it is a requiered field make sure something is chosen in the lostfocus or valid events - just like you would do with regular texboxes Arnon >All strange things used to happen in Friday. This is one of them. Imagine >that you open list portion of combobox, browse by mouse over there and >leave the area without selection (e.g. just click on some other control). >It's not very nice (but understandable) to find out that Combo.Value is not >corresponded to RowSource.Field anymore, but the worst case is that >Listitemid or Listindex properties go nowhere after this action. >Can it kill some App logics? I just tested this for 3.0b. >Any comments? > >