Our split Access 2010 database has been working nicely for years. It, of course, has lots of Richard Rost stuff in it like DLookUp() and Hyperlink Part 2 stuff in it.  Some of our users were upgraded from Win7 with Office 2010 to Win10 with Office 2016.  Something broke on June 13 while I was on vacation, keeping the blame off of me.  One of the Access 2016 users ran a Compact and Repair.  We are not blaming that person. Many of the queries that worked for years would not allow updates.  I put two of the offending tables into a blank database and with a single join (inner, then right outer join.  The query results were not updatable so, for the last couple of days, I have been using Richard's Expert 10's DLookUp() to avoid joining tables in queries.

Our office skipped Access 2013.  One coworker suggested we should have taken the Access 2010 files into an Access 2013 environment, then into Access 2016, thinking 2010 and 2013 could talk via XML. Then, go to Access 2106.  The thinking is that we missed some patch by skipping 2013 when we went from 2010 to 2016.  I saw some compatibility warnings on the 'Net after the fact, so I am asking this forum. Are there some issues?

If compatibility is an issue, how do I do cell-by-cell comparison of our thousands of records to find out what records have changed from June 13 until, say, I get a reply to help me? I was thinking of comparing the records, somehow (remove duplicates?) in Excel, one table at a time, using transposition.  That seems too crude, but I am pretty desperate.