Mike --

Thanks for the thought. Turns out it doesn't apply in my case.

I only have two tables I'm using this for.

One is for employees -- we're not Walmart, we only have 70 employees right now.

The other is a access control table. 9 records right now.

Thanks,

Jim


>>I did two things, which appear to have taken care of the problem
>>
>>(1) There was a controlsource on the combo which referred to the actual field in the table. I replaced that with a form property.
>>
>>(2) I also did a requery on the combo as part of the "add" command button.
>>
>>In combination, these seem to have taken care of the problem.
>
>Just a thought, a combobox gets slower as you add more rows to it. That, IMO makes a combobox as a navigation tool a questionable choice. There should not be built-in limitations on the number of records your system can handle, right? :)
>
>>
>>
>>
>>>>Naomi --
>>>>
>>>>That's exactly what I thought. That's not what's happening. And, the controls on this form are VERY simple -- nothing special going on behind the scene.
>>>>
>>>>Without using refresh -- the fields other than the combo show the old values, but you see the correct values when you click on the field. This I expected. The combo box still shows the original record, but does not change to the correct value when I click on it.
>>>>
>>>>When I DO use refresh -- the fields all show what had been the last record before I added a new record. Except the combo box, which is blank (but goes to that record when I click on it.)
>>>>
>>>>Curious, eh?
>>>
>>>What if you remove the combo for some time? Would it work?