No browsing doesnt take a long time per say, it's just that if you dont know
exactly which letter the product starts with you have to put in A and scroll
through tons of products, then B etc. etc. to try and find the one your
looking for with auto fill you need to at least know the 1st letter, our
product codes are not as straight forward as one would hope. Having a
wildcard (*blue) that will lookup all products with the word blue in it
because you know the product at least contains blue in part.
Do you mean that the combo takes a while to access all its rows, so
that browsing through the list isn't practicable?
You may be able to speed it up by changing the rowsource to just SELECT
DISTINCTROW ProductID, ProductName FROM Products ORDER BY Product Name.
Make sure the ColumnCount is 2 and the BoundColumn is 1 (assuming the
combo is designed for the user to select the ProductID, the first
column?).
In this case the Rowsource with the WHERE added in would be
SELECT DISTINCTROW ProductID, ProductName FROM Products WHERE
ProductName LIKE """ & [the text box name] & """".
(NB, to search for anything containing "blue" you'd have to type in
*blue*, not *blue - the latter will only finding things _ending_ in
"blue").
You'd have to put some scope for you to clear the contents of the text
box and view the whole list as well: e.g.
If Me.[name of text box]="" Then [name of
combobox].Rowsource=SELECT.....ORDER BY ProductName [without the WHERE
clause].
hope this helps.
Seb
ORDER BY Product Name