You can also do:
- Give a range of primary keys to every each copy of the database running on a different location. This way primary keys will never be the same on different locations.
- Add a field to the table and make a compound primary key (or add a prefix to the primary key if you don't like compound keys). This field or prefix indicate the location of the database.

With these techniques not only you avoid conflicts, but you know where the record was generated.

>Have two copies of a property table that I want to sync into a single table. I would on the property application at home, and my friend works on it at their home. We are both adding different properties and possibly modifing the same existing properties. We are not adding the same property.
>
>Guess I should change add_dt and mod_dt to include the time. Any matching key where the add_ts is different, then it is a different property. For any matching key where the add_ts is the same but the mod_ts is different, then is is a modification. Once i have a different add, I can renumber the key and replace. If it is a different modification, I will save the most recent modified date/time. Does this seem correct? Is there something that is more precise than date/time?
>
>Thanks
>
>Brenda