Look over the article Hilmar has referenced. Found quite informative when I developed similar process.

Becomes rather easy by having update, insert and delete triggers call a stored procedure that documents changes that are made. Been doing that for 1 1/2 yrs and presently sychronizing 13 different database's with 32 different sites throught out the state. Developed a simple routine to transmit xml packs of table changes that are sent to central office and all changes are then inturn submitted for each external site to retieve.

The only issue we have is when we have people from different offices on the phone expecting to see changes immediately. Presently it has a lag time of approx. 1.5 to 3 minutes before information gets to them. The beauty of this is that we loose internet connections etc. and does not disturb remote offices. They are able to continue and when connection is restored, in mater of minutes they are in sync again. We do have some individuals using laptops that are on the road and when they go on vacation for a week or so and come back, the time to sychronize can last up to 30 minutes (depending on internet connection speeds)

Good luck





>We are planning to develop a simple (but hopely robust) replication system for our software.
>We are using native DBFs, not SQL servers yet.
>
>Have you any suggestion before we commence?
>Any whitepaper out there?
>
>Googling didn't helped too much this time. O:-)
>
>Thank you.