Pare sia dovuto all'ultimo aggiornamento:
https://answers.microsoft.com/en-us/msoffice/forum/all/access-365-crashes-sql-server-fields-of-type/6b9eb767-6901-4ba0-ac78-6a00174223e9
' ===================================================================
Very soon, we will ship a new data type, known as Date & Time Extended,
which enhances syntax compatibility with SQL while increasing accuracy &
level of detail in date & time records.
While the feature is not yet enabled in Current Channel builds, most of
the code for the feature is in the product in an inactive state.
Nonetheless, we are aware of a problem that currently exists with this
new code. As of today, if you are on version 2005, build 12827.20010 or
greater, and you manipulate Decimal fields (Access
DataType=Number/FieldSize=Decimal, or SQL DataType=Decimal) using DAO
(Data Access Objects), you might have identified your app crashing. If
you hover a variable with the type in VBA code, you may see that the
field is not being displayed properly; either reading as ‘?????’ or
giving a Type Mismatch error, or Access may crash.
We are very sorry for the inconvenience this causes in your Access app.
The Access team is working on resolving this issue as soon as possible,
and we will report back to you once this error has been fixed. In the
interim, we’d recommend for you to roll back to a previous version
(
https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic),
or switch to a slower channel (e.g Monthly Enterprise Channel, or
SemiAnnual Channel), until the issue is fixed in Current Channel. The
issue only impacts Decimal types so if avoiding DAO code that
manipulates Decimal types is possible, we’d advise this as a short term
solution.