Re: Homegrown synchronization

I can't see the downside of doing it with updates instead of a
wholesale copy, especially given that you already have code written
that will work for it, right (isn't it basically the same code as is
running in the synch app to incorporate updates from the users into
the server back end?)?

Not quite, because the update file that the synch app takes has an
extra field in each table, UpdateorDeleteFlag. That field tells the
code whether to add/edit a record or delete it to/from the production
backend.

The code that I currently use to create the update file from MyApp
compares the current backend with a 'snapshot' of the backend at
session start. As I've mentioned I do this for the deletion checks.
This would probably be the code that I would use. Might require
modification for the add/update, but shouldn't be difficult. My
concern has been the time it will take, but you've mentioned now
several times about a tombstone table.


--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

.