Fix Access 2016 Type Mismatch Errors and Crashes After an Update
Question details
Resolve type mismatch errors or unexpected closures in Access 2016 after an Office update.

- Product
- Microsoft Access 2016
- Device & OS
- not provided
- Scenario
- An Access database uses DAO code to manipulate Decimal fields after an Office update.
- Observed behavior
- Access may report a type mismatch or close unexpectedly, sometimes without displaying an error.
If Access opens, select File > Account to note the version, build, and installation type. Check whether the affected database uses DAO to manipulate Decimal fields; the documented issue was associated with the Date and Time Extended data type.
Update or roll back the affected Office installation
Check for a current fix first, then use the rollback procedure appropriate for your installation if the problem persists.
Microsoft documented this issue in version 2005, build 12827.20010 or later. That historical build range does not mean every later build remains affected.
Click-to-Run and Windows Installer (MSI) installations use different update methods. Reverting an update can remove security fixes, so coordinate with your IT administrator.
In Access, select File > Account > Update Options > Update Now if that option is available. Reopen the database and test the action that caused the crash.
On File > Account, look for Update Options under Product Information. Its presence generally indicates Click-to-Run; an MSI installation typically does not show it. If Access will not open, ask your administrator to verify the installation.
For Click-to-Run, follow Microsoft's instructions at https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic and select an earlier build appropriate for your installation.
For an MSI installation, open Control Panel > Programs > Programs and Features > View installed updates. Identify the relevant Office update and check whether Uninstall is available; consult IT before removing it, because not every update can be uninstalled.
If your Click-to-Run subscription supports channel changes, ask IT to consider a slower channel, such as Monthly Enterprise or Semi-Annual Enterprise, using Microsoft's deployment guidance.

Avoid affected DAO operations on Decimal fields
Use this workaround when the database code can be changed or the affected operation can be postponed.
Use WPS Office for everyday document and spreadsheet work
WPS Office is a free, lightweight alternative with a familiar interface for working with common Office files. It can help you move everyday document, spreadsheet, and presentation work to another suite, but it does not fix Access or run Access databases and DAO code.

Frequently Asked Questions
Why does Access crash when DAO uses a Decimal field?
Microsoft documented an issue associated with the Date and Time Extended data type that could cause type mismatch errors or crashes when DAO manipulated Decimal fields. Check File > Account for your build and test a current update first.
How can I tell whether Office 2016 is Click-to-Run or MSI?
In Access, open File > Account and look under Product Information. Update Options generally indicates Click-to-Run; MSI installations typically do not show that control.
Can I use the Click-to-Run rollback instructions for MSI?
No. For MSI, check Control Panel > Programs > Programs and Features > View installed updates for the relevant update and whether it can be uninstalled. Consult IT before removing it.
Will changing the update channel fix every Access installation?
No. Channel changes apply only to supported Click-to-Run subscription installations and may require administrator deployment. An MSI installation does not use those update channels.
Can WPS Office run my Access database instead?
WPS Office is an alternative for documents, spreadsheets, and presentations, but it does not run Access databases or DAO code. Use Access-specific troubleshooting for the database.




