Solved Afterupdate with no update.

[CJ_London]

May be missing the point, but you can use the timer event - away from my computer at the moment but set the timer for say 1/2 second. Reset the timer on each key press. If user hasn’t typed anything for 1/2 second, assume they have finished

 

[The_Doc_Man]

In a previous multi-post thread with a (now-departed-but-not-deceased) knowledgeable forum member (who must not be named but she wasn't Lord Voldemort), there came a discussion about the factor that is going on here.

Someone has a particular behavior in mind and wants Access to do what s/he wants. But they made the design without considering the odd chance that it would be more efficient and less work if you could re-orient your thinking to follow the operational style of Access. Basically, if you know what Access does on its own, you do less work and get more results quicker (and maybe better?) if you let Access do its thing while helping you. We all talk about how Access is sometimes as dumb as a box of rocks, but it DOES know how to build database elements. It just doesn't know what elements you want to put and where. It doesn't know what to DO with your data. There, you have to step in.

It comes down to a simple phrase - either you go with the flow or you try to paddle upstream. This becomes a philosophical issue in that Access is a Rapid Application Development tool and - for better or worse - that rapidity is based on its designer's viewpoint of an ergonomically comfortable data flow, which for readers of English and many of the "Romance" languages, is a left-to-right, top-to-bottom reading order and writing order. It is ingrained into us by the way we read books. For that reason, TAB ORDER is ALSO left-to-right, top-to-bottom.

Any time that this order is not good enough, we will run into problems that require extra work. In the simplest case, the work is changing tab order manually via numeric entry or drag-n-drop. But there are other things that people do because Access "doesn't do it right" (by their standards.) For instance, UPDATE behavior on a form. Drop-down behavior in an FAYT environment.

This comes back to another principle. When all you've got is a hammer, everything will be treated like a nail. When all you've got is Access, you'll have to work harder when you are trying to do something that Access doesn't do naturally. And that is what is going on here.

 

[Albert D. Kallal]

Actually, if you note many times here? I just use screentogif for my posts. It's quick and simple.

As I pointed out, the issue REALLY comes down to HOW you going to know when the user is finished typing.

So, for example, in this dropdown, I type in the letter K - and auto complete will match the first "K" value.

Ok, so I hit the letter K in above. But, how do we know if I want to keep on typing - or is the first "K" value what I want....

I of course can keep on typing, such as: "K", then "i".

The problem still remains - how to know when the user is finished typing.

So, as suggested here, user has to hit tab key - that that's going to be the case for web based, or desktop, and it's been that way since day one of the windows (and web) GUI (that's over 30 year now!!!!).

So, as some suggested here? I suppose a timer - but EVEN then, maybe I do have to type more, and narrow down some choices. With part descriptions or what not? Often there is going to be quite a bit of typing until such time the match is narrowed down, and as noted, maybe I'm already happy with the choice I narrowed down, but then again, maybe not.....

Anyway, as a tip, and how I been of late posting animated images in my posts such as above? I use the free screentogif - it's fast and easy....
(in fact, I dare say that to make this post - barely any different time and effort compared to if the above gifs not been included)

Edit: as George pointed out? It's near always a bad idea to try and override the default windows GUI standard specifications and behaviors- really, it is!

R
Albert