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
One needs to remember that the problem was caused by a change made outside the Access codebase. But its Access that needs to be recoded. And that means making sure there isn't a domino effect from any code changes.
From what we have been told a fix will be available soon. I'm going to go out on a limb here and guess within this week. Which would mean just 2 weeks after it was reported.
Well,
again: Whatever the root cause was: The fact that MS shipped a product with such a serious bug in an elementary function means that they do not do tests and leave it to their users to find the bugs. It is really a shame. It is the same with Windows. About a month ago I moved to Windows 10 and it is the most unstable and bug-ridden Windows I have ever seen. Then, OneDrive is the worst bug-ridden cloud storage I have ever seen. And their is no sign of a change. MS does not seem to care, at all. Instead every software release of all of these products is worse than the previous one. If MS continues to act like that they will loose their customers really fast.
Oh, and still there is no patch for the Access problem...
Frank
![](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(89.60000000000001, 51%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
According to you we all have corrupted installation that cannot be repaired by reinstalling the product so maybe you can investigate a little deeper to tell us all what we can do.
Thank you
You need to have read further on! Scott McD's response that you replied was posted the same day as the original post. That was before it became known that this was more widespread than one user. As has been detailed further in this thread, this is a bug revealed by an Update to other Microsoft components. More importantly, several easy workarounds have been posted in this thread.
MoNeklawi,
Did you review this thread? You do not have a "corrupted installation", this is a bug introduced by a Microsoft update some 2-3 weeks ago. While we wait for them to fix the underlying root cause...
"There are very simple workarounds
http://www.devhut.net/2016/06/17/field-size-option-not-working-in-access-2016/
Using a SQL DDL query takes all of 1 minute, importing Tom's table takes about the same and then you simply copy/paste.
So at least we're not truly at the mercy of Microsoft for this one."