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)
Access 2016/Office 365
I go into my table, add a new field, set data type to Number, go down to the lower pane to set field size (which shows Integer by default), and THERE ARE NO OTHER OPTIONS.
NOTE: I'm adding a new field -- It's NOT a part of a relationship.
Typing in 'Long Integer' gives me a "The text you entered isn't an item in the list." error.
When I draw down the list of options for field size, it's all blank.
Makes no sense. I've done this a million times before, and now it doesn't work... I've repaired the database, and also tried repairing/re-installing Office 365, to no avail.
Suggestions?
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.
Until MS comes out with a proper fix, you can consult http://www.devhut.net/2016/06/17/field-size-option-not-working-in-access-2016/ for workarounds.
Fingers crossed MS addresses this bug promptly!
apparently wasn't using the right search terms... or the threads were buried in the chaff...
![](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)
The bug was only discovered this week it was first reported here on Saturday and confirmed by the Access Dev team on Monday. You would not have been charged if it was determined to be a bug.
Had you searched this forum you would have found at least 3 threads discussing it.
This is a bug in the June 7, 2016 update for the click-to-run version of Access. Microsoft knows about this bug, so hopefully it'll be fixed in the not too distant future.
*FACEPALMS*
I even called MS Support -- only to find out that basic Access Support (for non-contract, mind you) would cost me $495 minimum. I turned it down, thankfully. I would have been beyond IRATE to find that this was a known bug, which regular Tech Support doesn't know about.
This is a bug in the June 7, 2016 update for the click-to-run version of Access. Microsoft knows about this bug, so hopefully it'll be fixed in the not too distant future.
See Table design bug in click-to-run Access 2016 for a temporary workaround.