>Wish I could but at this point it really isn't an option. I'm flagging the record after its been changed was hoping for some ideas on checking for dups. thanks though

I know. It was probably the answer you were dreading. :-)

If I had to do this, I would do the same as you:
- time stamp every record
- primary key for all tables

Rules:
- add any new record (new primary key value) in a database to the other database
- any record that has changed can be copied over the correspond record in the other database without checking if the timestamp of the other record occured prior to the last synchronization.

The tough part:
1) If both sites have changed the same record how do you tell which site has the right or best changes. Perhaps your business will dictate this. In some cases the last change might win, sometimes the first change might win. I would imagine though that it is more complex than that.
2) What if both sites change part of the record. Site A changes the address and Site B changes the name. How can you detect whichs fields where changed and when?