Windows 11 Access Runtime 2016 32-bit, Autocomplete stops at row 1,000

Question

We are upgrading all computers from Windows 10 to Windows 11.

We have a Windows 10 PC with a .accdb file. It has a simple form with a combo box on it that should auto complete what the user is trying to type into the text box. The combo box is pulling data from a linked table with 4,300 rows.

I swapped out this computer with a new Windows 11 computer and brough over this file to the new PC. Auto complete is now cutting off at exactly row 1,000.

For example:
Row 1,000: ABC123
Row 1,001: LKJ565

ABC123 will auto complete. LKJ565 will NOT auto complete.

I have confirmed that both computers are using the same exact version of Access Runtime 2016: same bitness, same build number.

M365 Access Runtime on the Windows 11 PC does work for the autocomplete, but I don't want to introduce new issues when trying to fix this one, so ideally I would keep using Access Runtime 2016.

Things I have tried:

-Installed VC++ Redistributable to match what the old pc had
-Ran compact and repair

-Repaired access runtime

-Changed "Don't display lists where more than X records" to 10,000

-Disabled hardware graphics acceleration

-Tested with imported and linked table

-Tested on another Windows 11 PC (still does not work)

Answer 1

Hi,

There are several variations of this issue spanning many years. The "worst" one, which occurs only with Windows 11, was fixed in 2024, though only for M365. That would explain why it doesn't happen in the 365 Runtime, which is the only Runtime that Microsoft keeps up-to-date.

In 2024 we reported on the bug and the fix on the AccessForever blog, as well as on the Dropdown workaround that many people have used successfully.

Servus
Karl

---

Access Forever, News, DevCon
Access-Entwickler-Konferenz AEK

Answer 2

Hi Ryan,

Thank you for the detailed information and for testing this across multiple systems.

Based on what you described, this does not appear to be an issue with the database file, the linked table, the number of records, or database corruption. Since the same .accdb file works correctly on Windows 10 with Access Runtime 2016, but fails on multiple Windows 11 PCs with the same Access Runtime 2016 version, the behavior appears to be related to compatibility between Windows 11 and the older Access Runtime 2016 combo box AutoComplete/AutoExpand behavior.

The key finding is that the same database works correctly on the Windows 11 PC when using the Microsoft 365 Access Runtime. That strongly suggests the issue has been addressed in the newer Access Runtime, but not in the Access Runtime 2016 codebase.

At this point, my recommendation is to move the Windows 11 systems to the Microsoft 365 Access Runtime after testing the application on one pilot workstation. This would be the most reliable and supportable path forward. Access Runtime 2016 is also at the end of its support lifecycle, so continuing to use it on new Windows 11 deployments may expose me to additional compatibility issues over time.

If you prefer not to move to Microsoft 365 Access Runtime immediately, you can look at a temporary workaround in the Access application. One option is to adjust the affected combo box behavior so the drop-down list opens while the user types, which can help bypass the AutoComplete limitation. However, this would be a workaround rather than a true fix, and it may slightly change the user experience.

Recommended next steps:

1. Install Microsoft 365 Access Runtime on one Windows 11 test PC.
2. Test the affected combo box with values before and after row 1,000.
3. Test the rest of the Access application, including forms, reports, linked tables, printing, exports, and any VBA automation.
4. If testing is successful, standardize the Windows 11 machines on Microsoft 365 Access Runtime.

My recommendation is to start with a pilot test of Microsoft 365 Access Runtime, since it has already resolved the AutoComplete issue in your initial testing.

Note: Please understand that my initial response does not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution.  

I hope this information is useful.

Thank you again for your time and for raising this important usability concern. If you have any further questions or need additional assistance, please don’t hesitate to reach out. 

I look forward to your thoughts on this. 

---

If the answer is helpful, please click "Yes" and kindly upvote it. If you have extra questions about this answer, please click "Comment".      

Note: Please follow the steps in forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.