Cetin and Ajay: I'm working on a project like this, and finally decided to use a log file which would be the only file transmitted either up to the main office or back to the branches.

1. Each field has a call in the LostFocus which checks if it's been changed.
2. If yes, an entry is made in the log with date, time, field name, table name, dbc name (if using more than one) old value and new value and field type (I store all values as character data). One record per field, updated if a previous change is recorded.

3. Records are added to the log for any deleted records, with the unique ID stored as field/field value and a code for "Delete this record".

4. Entries are also made if there are any cascaded updates/deletes.

5. The log file is uploaded to headquarters. All the logs are appended into one giant file and indexed on date/time. Then the appropriate changes are made to the master file.

6. During the update, a new log is written with only one record per field (There could have been several records in the uploaded logs for any one field, one from each office.)

6. Finally, download the new log to each office where they run it first thing in the morning.

7. We do have a problem with an office deleting a record which another office still wants. The client will have to decide how they want deletes handled. At this point we are not sending deletes out to the other offices, and are simply ignoring them. The code is there in case the 'rules' change.

We're working on automating the whole thing, so the users only push a couple of buttons.

Sorry this is so long (One of Vlad's 'sheets') but I couldn't condense it much :-)

Barbara

>The best I can think of is to take advantage of the data/time
>fieldtype.
>
>Compare the central data at the end of the day
>with the local data and make a fresh set of data.
>
>and finally distribute all the newdata back again at all location.
>
>It would also be interesting to see other solutions from fellow
>members
>
>Ajay Sanghani
>WinSmart Solutions
>Building Softwares Better and Faster !
>http://www.winsmart.com
>
>
>
>>One of my clients use a finished app on more than 5 independent locations. There is no connection between these locations (they don't want to use online options). They want to deal with their customers from any location. At the end of the day they want to synchronize data on all locations (deletions, additions and editing). They guarantee that on a given day a particular customer's data would be edited, added or deleted from one point only. I have a lot of tables and relations but any add, edit or delete operation takes care of cascaded updates. Calculation and balance data are managed through local views. I developed a stategy to do job but seeking a better way.
>>Thanks
>>Cetin