> On a no hit, I use oApp.doformretval() to call a 'NewRecord' class to enter a new record. (this last step depends on your application). Upon return, I set the .DisplayValue to the returned value (the control source).
>>>
>>>For some reason, I couldn't get it to work with a SEEK(). But the functionality turned out to be more straightforward using a SELECT.
>>>
>>>HTH
>>
>>
>>Matt,
>>
>>I have the array created. When I try to select a new customer the combo stay on the first record. This is not changing at all. What did I miss?
>>
>>Thank you
>>Holly Clawson
>
>If you're using the same/similar code that I did, a new customer (no hit) should bump the array down to one element: the new customer. In which case the first item is correct. Maybe I didn't explain that right..sorry.
>
>HTH
>
>BTW, keep in mind, Ed thinks there's a better way. He could be right. I'm anything but an expert with comboboxes.
>
>Matt


Matt

I can not get this to work. How is it that Ed say to do this. It can not be that fricken hard to have a combo box, with all you customers in it, and add new customers to this field.


Thank You

Holly