>>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?
>
>Yes, a bit more elegant.
>Don't delete any records.
>Add an "active" logical field and default to .T.

How did you choose to implement it?
Were you able to get this working?