Forum Discussion
Problem with combobox form controls
A fix for this problem is in the works. See this AccessForever article.
Hi GustavBrock ,
I have experienced a similar problem with the MS Access combobox on Win 11, however, my problem is that the auto-expand feature stops working beyond the 100th row. So if the initial text that I type is the start of any one of the first 100 values of the bound column, then auto-expand works fine, however, when typing the initial text of the values for rows 101 and beyond, I get no auto-expand result.
Our respective experiences seem to indicate a possible difference between Win 10 & Win 11 for the MS Access combobox. I have been putting up with this problem for about a year and a half, after I changed from Win 10 to Win 11. I had tried searching the web for a solution a few times since encountering the issue, however, it never occurred to me that the underlying issue could be the difference between Win 11 & Win 10. I'm sorry that I do not have any solution to offer for this apparent issue with the MS Access combobox on Win 11, however, I thought it was worth posting a reply in support of your issue because this is a very a similar issue for me too.
FYI, the row sources of my bound columns are queries of tables, and the columns being bound to are of type text. I have 3 combo boxes that are affected: two with 261 rows in the rowsource, and one other with around 10,400 rows for the row source; and hence I hit my problem of this apparent "100 row" limit on auto-expand.
Regards,
David.
I have the same problem on Windows 11 and Combo box only autoexpanding first 100 rows in query. Has any progress been made on this? Any workaround? wove5
- Oh my Good!!!
I can't belive it....
You don't imagine how many hours I have spend trying to find a solution or, at least, to identify the culprit... Thanks a lot!! My apologies. I should have updated this discussion some time ago. My excuse is that finding things on this forum is less than intuitive sometimes.
A fix for this problem is in the works. See this AccessForever article.
To add my 2c to this, which may help someone with diagnosis. I have just hit the same problem (in the last couple of weeks) using Access 97 (32-bit, of course, and yes I know it is old) on Windows 11 Pro. Combobox autoexpand stopped working, and using the SELECT DISTINCT workaround (suggested above) got it working again but only for the first 100 listed items, after that it fails.
This is a new problem which has suddenly appeared on this machine, it was working fine (under Windows 11) until recently. Still more strangely, the same database still works fine on another Windows 11 machine (also fully updated, as is the first); that is, on that machine the Combobox autoexpansion seems practically unlimited (thousands at any rate).
- Interesting, that was what I suspected. My fear is that Microsoft will stop supporting 32-bit Office installations at some point. I will report a bug if I can figure out how, but long term, I would recommend finding substitutes for any 32-bit controls. I would guess you're using some ActiveX controls. I had to replace most of mine last year for reasons unrelated to this particular bug.
- 32 bits, as I'm using some 64bits incompatible controls...
JF_Ruiz are you using a 32-bit or 64-bit installation of Access/Office? I am following this issue on another forum since autoexpand has worked fine for 25 years and this is frustrating a lot of users who upgraded to Windows 11.
I have yet to find a common denominator, but it does appear to be worse on 32-bit installations than 64-bit. For now, I would recommend adding the .Dropdown method in an OnChange event. That is a good enough bandaid for me until there is enough information to report this to Microsoft as a bug.
- None that I know
After a long time, I realized that the problem is somehow aleatory. Sometimes a combo work and another don't, later is that one the one broken and first one work, Also if you expand the box and move down an up with cursor it select a different record than the one you chose (greyed)...
I'm completely mad with that...
