I have built a small Access database with a few tables. The data is stored in several SharePoint lists linked into the database (so changes to the list are reflected in the DB), and the Access file itself is stored on a SharePoint server. The file format is .accdb.
Upon opening it, Access prompts to save changes to the server. As the data is stored outside the file itself, there aren’t normally any changes to the file content itself—unless someone were to modify a query or report, which is rare. (I am aware that the Jet database engine treats a mere open operation as a modification, thus there’s no true read-only mode.)
Originally the file was some 8–9 MB in size. Over time, the file grows in size and has at one point broken the 100 MB barrier. After running “Compact and Repair” on the database, the size is back to the original 8–9 MB.
Users have a mix of Access 2010 and 2013 running on their PCs.
What is causing Access to inflate the file like this, and how can I prevent it?