To Merge OR Not to Merge

[Guest]

Im working with two databases that have basically the same information. Im
trying to put the information from both Db's into one database. I was
thinking about putting the info in two seperate tables,but i'll run across
the issue of duplicate data.
Does anyone know a better way i can go about doing this?

 

[ChrisM]

Im working with two databases that have basically the same information. Im
trying to put the information from both Db's into one database. I was
thinking about putting the info in two seperate tables,but i'll run across
the issue of duplicate data.
Does anyone know a better way i can go about doing this?

If the data is essentially the same, why can't you put ALL the data into a
single table?
You might have to add a column or two, or even change your design slightly,
but long term, it makes much more sense to have it all in one place.

 

[Craig Alexander Morrison]

The BEST way is to keep ONE copy of data otherwise how do you know which
copy is correct?

Put the data in one DATABASE and continue to use two APPLICATIONS.

If you have two Access/Jet MDBs with this data then create one MDB
(back-ends or database) with the merged data only and if required create two
addtional MDBs (front-ends or applications) that use the same data but
perform the specific roles that your current twin databases/applications
perform.

IOW If you have two MDBs now you will end up with three but only ONE will
contain the data.