merge two same databases

[Guest]

I have a database in access. We have different copies of the data base on 2
computers so we can enter the infor more quickly. When finished I would like
to merge the information into the other database without losing the
information on the first database. They will not be working with the same
entries but they are working within the same database. For example the table
has a line called AB which the user on database 1 will modify. The user on
database 2 has a line called CD which the user will be modifying. I would
like to merge the databases so that AB and CD, as changed, are on the same
table.
Thanks!!

 

[Jeff Boyce]

Rick

More info, please...

Are you saying that the folks using the two separated dbs NEVER touch the
same record(s)? If so, one approach might be to: add a field that stores
who is updating the record (for each record); open one of the dbs and link
to the other; create an update query that ONLY updates the records "touched"
by the other db's person.

Have you looked into using a shared db (if the two are on the same LAN)?

Have you looked into Replication (if the two are not on the same LAN)?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Guest]

Here is the scenario
Our database has several tables. It all deals with property taxes. In the
main table, called List is each property. Information on each line needs
changed. They are linked to information in different tables, but it does not
affect the other.
For example property x needs infor updated in the list. Info about property
x is updated in another table called subsequent year's taxes. But although
the information is in the same table, it is never for the same property.
We lost our database in a server crash. So it is too much information for
one person to manually enter. I was thinking I might be able to put two
people on it, each working with a separate list of properties, and then merge
them into one list.

Thanks for your help!

 

[Jeff Boyce]

Rick

So you are confirming that the records touched by person A will never be
seen by person B, and vice versa?

If that's the case, to re-combine the data into one table, open one of the
..mdb files, link to the other to get the "other" table, and do an append
query to add the records to the List table in just one of them. Delete the
link.

That one's your single db (after all the second db's records have been
appended).

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Guest]

Not quite.
What I want is for two people to work on the same copy of a database, but
then merge them into one database. The ability to "see" the data isn't the
issues. It's kinda like giving several people pages of a book to type but
when they are finished it's all one book.

 

[Jeff Boyce]

Rick

I suspect you and I are saying the same thing, differently.

Person 1 will not touch the "pages" (records) that Person 2 is working on.
And vice versa, right?

Take another look at my proposed solution...

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Guest]

yeah we're saying the same thing. Thanks!

I know nothing about Access, so can you translate your response for a person
who is not even a novice?
Thanks again!

 

[Jeff Boyce]

Rick

Access has a lot of features and functions that may help you on your
project, but it has a fairly steep learning curve, too. Are you sure you
want to invest your time/effort learning enough about Access to get this
task done?

Another approach might be to provide each of your "book reviewers" a set of
(their own) records to review/revise via some other software tools with
which you and they have more experience. A spreadsheet (or even a Word
table) comes to mind...

Regards

Jeff Boyce
Microsoft Office/Access MVP