>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.
You want changes to be updated immediately to another folder, right?
You might put a trigger in every table, which calls a generic function that does the replication.
My article on "audit trail" explains how to record changes done to tables; perhaps you can adapt it. The examples show only the basic principles; the audit trail is not in a format that can easily be read by machines, so some adaptations are required.
One possibility would be to have a machine-readable version of an audit trail, and then recover from there, to a backup database, when you need to do it.
www.utmag.com, May 2003.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
