Hi Mike,

Long time!

Also thought about this. Just cannot figure how this work for deleted records? Say my Products have 56 rows, then it is dumped to the branches. Great. Then, a few Products were removed at Head Office - no timestamp will be recorded here. This means the update algo should be "two-sided "- one needs to check the new timestamped records from Head Office - and also - use Branch Products to check against the entire Head Office Products for any missing ones for deletion, right?

Is there a more elegant way? :)




>>Hi Guys,
>>
>>Basically, I am doing a POS app which will be used by a handful of branches and one head office. All will be connected via internet.
>>
>>We would like for the following to be implemented:
>>
>>1. Whenever head office say creates, deletes or modifies a new product, it will be propagated to the Products table of each branch.
>>
>>2. Conversely, branch sales data feeds are pushed to the head office.
>>
>>3. In the event that internet connection fails during this "synching", how does one know where "we left off" to continue?
>>
>
>It sounds like you don't really have two way sync
> Head Office updates one table
> Branch Office updates the other
>Sure sounds like two one-way syncs
>
>
>One way sync is easy.
> Put a lastupdated datetime field in each record.
> Put a trigger to update the lastupdated on create, update, delete (usually an 'active' flag in my systems)
> Each side asks the other for all records updated since the last sync. (Be sure to NOT change the lastupdated field when syncing)
>
>Best if each computer is atomic clock synced.