unique key conflict with a mirrored table

[alekfelstiner]

Here's my setup:

One table ("Contacts") stores individual contact information, with each
record automatically assigned a unique key ("Contact ID"). However, I need
another mirror table with the same information in order to track referrals
(i.e. Contact #1 is listed as the referrer of Contact #2). So I created a
mirror table ("Contacts Mirror"), which is meant to hold the same basic
information (Contact ID, First Name, Last Name). The "Contact ID" field of
the "Contacts Mirror" table is joined in a one-to-many relationship with the
"Referrer" field of the "Contacts" table.

When users click the "Save Contact" or "Delete Contact" buttons in their
entry form, they are triggering a macro that runs the following:

1) a Delete Query clearing out the "Contacts Mirror" table
2) an Append Query that refills the "Contacts Mirror" table with the current
contents of the "Contacts" table.

With me so far?

I have people entering information on a few separate computers, and I
synchronize to the master every few weeks. Unfortunately, when I go to
synchronize I get unique key conflicts for everything in the "Contacts
Mirror" table, and only that table. In other words, the matching unique keys
for Contact #1 in the "Contacts" table itself don't produce a conflict, but
they do produce one in the "Contacts Mirror" table.

What's going on? Is something in the Delete/Append process creating issues?
Is it the relationship between the "Contacts" and "Contacts Mirror" tables?
I'm at a loss to fix this, and the size of the database is growing to the
point where resolving the conflicts manually is too cumbersome.

I appreciate any help. Thanks!