Hello friends of VBA

I have a search form that is populated by one of 6 different sources depending on a option group selection. (Eg. Names by First then Last, Names by Last then First, etc..) The option group is set to keep "Names by First then Last" as default. But while using the form, there are times when I begin typing and realize that I only know the last name of this individual, and need to select the second option. However, as I already typed into the ComboBox, selecting the second option triggers an AfterUpdate event of the ComboBox, and the code that follows is a selection and closing of the search form.

I would like to find a way to stop the AfterUpdate event when the focus is lost. This should be a simple thing, but my head isn't working it out so I thought to give someone an easy one.

Please note that the problem only exists if a user begins to type. Simply moving into the box, and then moving back to change options works fine. The moment the box becomes dirty, the loss of focus triggers an AfterUpdate event, even if the line is completely erased.

What I tried:
I noticed that if I backspace first, but not enough, the resulting letters are "not in list", which means I have to backspace completely. So I tried using a key press event that tests for the Backspace (Ascii = 8), using that to set a variable to true, which I then test for in the AfterUpdate event. This works okay, but it is clumsy and doesn't take into account that a user could erase in a different way: (Home/ Delete) or (Mouse Select/ Delete).

I also tried to use the Click event instead of the AfterUpdate, thinking it would not be triggered by the lack of focus. It is so triggered.

I had hoped the ComboBox events would be in this order: LostFocus, AfterUpdate.
But even though the lost focus creates the AfterUpdate the actual order is the other way around.
Orders like this: [ComboBox].BeforeUpdate, .AfterUpdate, .Click, .LostFocus, [Frame Option Group].Enter

The BeforeUpdate seems plausible, but what do I test for? If typing has begun, the value in the textbox is legit. If it was all erased the value will be Null. That works.
But what if the user doesn't erase anything, types 'J' for example, gets John Doe as the first item in the list, realizes they don't know the name and clicks above for the Lastname first option. The test for null will not work. It would work if I could test to see that the focus left the ComboBox, because that is legitimately what happened. But the focus is still shown to be on the ComboBox until the updates are all complete.

Ideas?

Thanks for your help?
GaryJ