Error code 13 - not programming, rather office system problem

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.