Quite a few questions need to be answered by you, before you undertake such a process
1 What is your back end ? Dbfs - sql ?
2 What is your communication protocal? odbc ado ftp http ?
3 How large is the data base are the clients' going to have a full copy ?
4 what is being sent back to the server, New records or just updates or both?
5 Have you worked out what to do if the same record is updated on the server, before the client updates it remotly.? who / or what record takes the override ?
6 When you update the server, is a new copy of the dbf's going to be made avail for the remote user ?

These are just a few questions which you need to consider as you work your way thought such a process. Most of these questions are not / programmer related, but more a business practice. Then you write your application based on the answers to the the requirments at hand.

Once you know in your head, how it suppose to work, than coding it (at least for me becomes quite simple.) Break it down into smaller steps. Your answers are right there in front of you.


Bob Lee



>I'm planning to develop a distributed application, which will periodically update the master database.
>
>That means, users will update their local database and later on the data will be synchronized with the master database on remote server.
>
>Can anyone guide me on the best practises on these type of development.
>
>TIA