We are receiving these errors, too. Here's our scenario:
1) Source: MS Access 2010 database
2) Destination: MySQL Database
3) Straight copy of data from Access to MySQL using an ODBC connection to the MySQL db on a separate server
The copying action stops with an "Overflow" alert, and nothing is copied. We narrowed down the first error to one particular record ... nothing special about it, it doesn't have anything hundreds of other records don't have, and those other records are being
copied just fine ... but not #63655. 63654 is fine, and 63656 is fine, too.
There are no calculated fields, nothing fancy going on, just a straight copy between tables with the same definitions.
This Access database has been used by our company for over 10 years, upgrading it to new versions of Access as they come out. If it was truly the case that there is a problem with the value size, then how did it get into the database in the first place?
Shouldn't there have been an "Overflow" error when, say, a long integer was placed into a short integer field? And why only this one record?
There is clearly more going on than a simple mismatch in value size. Where can I find more details about what other events/conditions might trigger this cryptic error? Thanks.