Yes.
One way is to create a simple application for the purpose. This will connect to the ACCESS databases in pairs and then, for each table, it will do something like the following:
INSERT INTO Left.Table(Columns)
SELECT Columns
FROM Right.Table
WHERE PrimaryKey NOT IN
(SELECT PrimaryKey FROM Left.Table)
Clearly, the above is pseudo-SQL; I haven't played with ACCESS for ages, and haven't connected to it ever from a .Net app. In particular, my shorthand 'Left.Table' and 'Right.Table' almost certainly will not translate directly into anything ACCESS accepts (if you were working with SQLServer there would be a variant that
would resemble that shorthand; but you're not).
You may even have to use an intermediate .Net object collection, and separate the above query into two (or even three) steps: (1) get the set of left primary key values); (2) get the set or right rows whose primary keys are not in the left set; (3) insert those rows into the left database.
Once you've done this for one pair repeat it for the result, plus the next unprocessed database, until you've merged them all.
Another approach that I think you could do, in MS Access itself, is to select one database as the merge destination (making a copy of the original, first), then: link to each of the tables in one of the other database, and run the above pseudo-sql (where the 'right' table is the linked table'). Delete the links, link to the next database, and repeat. This is the same as the .Net variant, but perhaps is simpler because you're not creating a whole app just to move data.
Submit an article or tip