This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
MS Access 2016 MSO (16.0.6925.1016) 32-bit
via Microsoft Office 365 Personal Subscription
Used on Windows 10
BUG:
The Field Size drop down combo for Number data types no longer displays values. An empty (white) drop down area appears but no values are visible in it. This make is impossible to specify the type of Number field (Double etc.) when creating or modifying a table.
Is MS aware of this bug?
Is there a fix for it?
I've been successfully using MS Access for some time now and this bug just recently appeared in the last day or so. I suspect a recent update may have broken the application.
Mark
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hey everyone,
Here's more information on the latest Office 2016 update: Announcing June feature updates for Office 2016 for Office 365.Current version (counting Tuesday's security update) is 16.0.7070.2022.
Updating to this build (if you haven't yet done so) should solve the number field issue.
Thanks!
I'm glad to see that the fix for this problem is included in the latest Office Updates.
For those with a Microsoft Office 365 subscription, open Access then:
File -> Account -> Update Options -> Update Now
and your copy of Office 365 will be updated, including a fix to Access.
It's great to have MS Access, one of my favorite applications, working as expected again.
Mark
Frank,
In recent months, if not years, MS' QA had gone out the window. Update after update that fixes one problem to crash another application or cause even more problems. New versions (think of Access 2016) released with MAJOR bugs. MS seems to have adopted a philosophy of testing on the users and fixing it if and when people make enough noise (the squeaky wheel gets the grease approach). They truly are no longer the company they once were, sadly!
Microsoft is still a great company, but I am surprised that it is taking so long to push out a fix for this major bug. I guess compared with Word or Excel, there are relatively few Access users.
I love to code initial versions of software using MS Access as the database because it is so easy to test and modify as the application database is evolving. Once everything is working, I develop a second version using SQL.
Frank,
In recent months, if not years, MS' QA had gone out the window. Update after update that fixes one problem to crash another application or cause even more problems. New versions (think of Access 2016) released with MAJOR bugs. MS seems to have adopted a philosophy of testing on the users and fixing it if and when people make enough noise (the squeaky wheel gets the grease approach). They truly are no longer the company they once were, sadly!
Hi Scott,
thanks for your answer. My point is: Whatever the cause is. If MS would have a test department they would immediately see that it is not possible to assign a data type to a number field. I really do not understand why they did not see this before the program was released. I am a programmer and technical architect with a very large company and the first thing we do is write automated GUI tests that test our software on each and every commit to the repository. Such a bug must not go unnoticed. Never.
Regards,
Frank