Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Last Updated: June 24, 2020


In version 2005 Of Microsoft Access build number 6.0.12827.20010, if you manipulate Decimal fields (Access DataType=Number/FieldSize=Decimal, or SQL DataType=Decimal) using DAO (Data Access Objects), Microsoft Access may crash. If you hover a Field variable with Decimal type in VBA code, you may see that the field value is not being displayed properly; either reading as ‘?????’ or giving a Type Mismatch error, or Microsoft Access may crash.


This is now fixed in all affected channels.

For Current Channel, version 2005, the issue is fixed in build 16.0.12827.20470.  You may need to force a manual update to get the new version.

For Current Channel (Preview), version 2006, the issue is fixed in build 16.0.13001.20198.

Icon Experts (brain, gears)

Ask the experts

Connect with experts, discuss the latest news, updates, and best practices, and read our blog.

Microsoft Tech Community

Icon Community

Get help in the community

Ask a question and find solutions from Support Agents, MVPs, Engineers, and other Office users.

Office Forum on Answers

Icon feature request (light bulb, idea)

Suggest a new feature

We love reading your suggestions and feedback! Share your thoughts. We're listening.

Provide feedback

See Also

Fixes or workarounds for recent issues in Access

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!