MS Access 2016 No Longer Displays Field Size Options

Anonymous
2016-06-11T10:04:09+00:00

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

Microsoft 365 and Office | Access | For home | Windows

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.

0 comments No comments
Answer accepted by question author
Anonymous
2016-07-15T22:57:30+00:00

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!

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2016-07-07T20:31:36+00:00

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

Was this answer helpful?

0 comments No comments

47 additional answers

Sort by: Newest
  1. Anonymous
    2016-06-12T02:14:20+00:00

    WORK AROUND

    While we wait for Microsoft to discover this bug and release a fix, here's one crude work around for setting the Field Size of a new Number Field:

    Select: File->Options->Object Designers

    In the Table design view section use the Default number Field Size ComboBox to select one of the following:

    Byte, Integer, Long Integer, Sing, Double, Decimal, Replication ID

    Then click "OK" to save your options

    When you return to the Table designer and create a new Number field it will now default to your selected Field Size.

    Every time you wish to change Number Field Sizes you will need to return to Options and re-select the appropriate default Field Size.

    This workaround will not allow you to change the Field Size for existing number fields. 

    It is also possible to use SQL DDL to create a new table using commands.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-06-11T22:51:57+00:00

    Me too, I was thinking ****, fresh install today. I thought it was just me that was broken. New fields of the numeric type are forced into long integer, and when you ->design view pull down field size, what an empty drop down? Shouldn't there be options like Double and Float etc... Most M$-users probably aren't aware of access so this will probably be ignored at best, unless of course a few corporates start kicking up

    PS The only foobarred updates I've had were '.net 4.6.1' which went into an infinite loop - quite common apparently. Obviously a sign of quality engineering ;) and of course KB3035583, but I barred that one and a few others 

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-06-11T18:53:05+00:00

    As a follow-up ... I went to Program Features and performed both a Quick Repair and Online Repair -- which appears to be an complete automated uninstall and re-install of Office 365.

    None of this solves this issue.

    THIS IS A MAJOR BUG THAT PREVENTS ALL ACCESS 2016 USERS FROM CREATING OR MODIFYING TABLES WITH NUMERIC FIELDS.

    Hopefully Microsoft is monitoring this thread and will create a hot fix.

    Mark

    Was this answer helpful?

    0 comments No comments