Merging two sets of tables

[Guest]

Hello, prior to a user error occuring, i had one large (120MB - Access 03)
database comprising of about 15 seperate tables. The database has now been
cloned and because of this, for the last month some users have entered data
on the original and a handful have entered data on the copied version.

Is their a way to merge both tables so that newly input data entered into
the cloned database can be transfered into the original database, resulting
in no loss of data?

Regards,
Tom

 

[Brendan Reynolds]

There's no automated way. It's a manual process. You'll need to open one of
the database, then link to the tables in the other database (from the File
menu, choose Get External Data then Link Tables). Now you can create append
queries to append records from one copy of the table to the other. The exact
details of how you go about creating those queries and handling conflicts
and relationships are specific to your data.

Make sure you have reliable backup copies of both databases before you
begin. It's also worth making further backup copies at intervals during the
process. For example, when you are happy that you've got Table A sorted,
make a backup before you move on to Table B - especially if Table A and
Table B are related. That way, if something goes wrong, you won't have to go
all the way back to square one.

 

[Guest]

Many Thanks Brendan

There's no automated way. It's a manual process. You'll need to open one of
the database, then link to the tables in the other database (from the File
menu, choose Get External Data then Link Tables). Now you can create append
queries to append records from one copy of the table to the other. The exact
details of how you go about creating those queries and handling conflicts
and relationships are specific to your data.

Make sure you have reliable backup copies of both databases before you
begin. It's also worth making further backup copies at intervals during the
process. For example, when you are happy that you've got Table A sorted,
make a backup before you move on to Table B - especially if Table A and
Table B are related. That way, if something goes wrong, you won't have to go
all the way back to square one.