Forum Discussion
Error code 13 - not programming, rather office system problem
I have Access code that has run perfectly for over 15 years.
Suddenly it started failing with Type Mismatch error with a simple SQL SELECT statement.
All the fields but the key field in this SELECT are numeric, but when I try to move value from one field to a temporary field (also numeric), Access hangs for a few seconds, then crashes out.
I took this Access file (.mdb) to a different system and it worked perfectly. This led me to believe it is an Access system problem.
Help most appreciated.
- I wonder if you're suffering from
https://www.devhut.net/2020/06/08/access-version-2005-build-no-12827-20268-causing-problems/
GreatDaneMusic Sometimes things change, data can be added to a table that no longer meets expected values or data types. An update to Windows or to Office can change features or functions in unanticipated ways. However, trying to diagnose such things from a distance (we can't see the mdb in question, nor the computer where it does and doesn't work) can be hard.
So, in this case, one of the things we'd need to identify (and potentially eliminate as your problem) is the version of Access on both computers and whether they both have the most recent updates. Also, we'd want to know if this is a self-contained mdb in a single file, or if it's split into an FE and BE.
From there we can move on to other potential factors.
Thanks for providing sufficient detail to help.
Thank you for your response.
<...data can be added to a table that no longer meets expected values or data types>
For this table, I deleted all data and re-entered manually to be sure.
<...the version of Access on both computers … recent updates>
2016, and yes, all recent updates are installed.
<...this is a self-contained mdb in a single file...>
Yes, it is.
Also, I ran Office Setup and this seems to have TEMPORARILY fixed the issue. It returned the next day.
Help most appreciated.
By far, the most likely reason for a "Data Type Mismatch" error is data that is not in the expected data type, i.e. a decimal value in an integer field, a string in a number or date, and so on.
The fact that it worked once, then doesn't again, suggests a closer look at any NEW data you are now trying to process.
- I wonder if you're suffering from
https://www.devhut.net/2020/06/08/access-version-2005-build-no-12827-20268-causing-problems/I think you are absolutely right! Unfortunately, none of the techniques I read to "downgrade" an office installation worked - none would run. I guess I have to wait until update 2006.
Thank you.
Good news! You were absolutely right! After the last office update from Microsoft, the problem is resolved.
Thank you for your help.
