I've had users at two different locations of a single company using two
different databases. One database was used to track assets and their
details. The other was used to track people and their details. From time
to time, I've ex****ted the changes in the People table of the People
database to append to a people table in the Assets database. So, the
people
table is in common, with consistent field names and IDs in both databases.
It's called People in both databases.
Now it's time to marry the two databases and my concern is that the Assets
database has a lot of relation****ps built up with its local version of the
People table.
The Assets database has not yet been split. The People database is split
with tables in one MDB file and front end items in a different MDB file.
The Assets MDB has 19 tables and the People MDB has over 40. Both have a
complex web of relation****ps.
What strategy would you use to combine the two databases? Is it possible
to
maintain the table relation****ps?
