>I have a few offices running the same application. One of them need to be able to get updated by the other offices entries on a regular basis (each hour for example). What would be the best solution to do that ?
>
>Thanks for any idea
>Eric


Eric,

Indeed many options exist. However, I think it is rather easy to tripple over the existing "sync"-options of today;
I always tend to lay them aside, and first think of the logic, and after that I may come to the solutions of "today".
Now in reality this will never happen anymore for us, because long time ago we created our own solution, which IMO is juist the normal one from 30 years ago :
Transactions

What we have -and IMO you should start thinking for teh logic point of view- is the output of your system of transactions, or IOW, the records written to (deleted too of course) should be captured and put out via a protocol.
I thing SQLServer can do this by its own and maybe even W2K has these possibilities (just no experience on it).
Creating it yourself is even possible without triggers (as how we have it), but take a year. Mind you, this can be done without any overhead when the outward-interface isn't used.
Of course you must be able to direct one transaction to more recepients, and therefore have to keep track of it per recepient.
Once you have something like this on native dbf, you have a roll-forward (and even roll-back) too ...

Again, the above just for the general thought on the logical approach.

Cheers,