Thierry,
OK sounds good. How should I proceed to test this?
Regards,
Koen

>Sure, you can pair the synchronized DBs the way you want; eg.:
>- central = web app
>- central = subsidiary 1
>etc.
>
>subsidiary 1 will get web app changes after sync into central.
>
>>Hi Thierry,
>>
>>I am in for a synch class which synchronizes tables with the centraldatabase not behind a Web Application just on a central server, suppose that would be possible with FiC?
>>
>>Regards,
>>
>>Koen
>>
>>>Hi Dennis,
>>>
>>>FoxInCloud includes a synchronization class that does all your requirements, including support of
>>>- deleted records
>>>- sync set of tables or full database (top-down using relations)
>>>- 2-ways or either way
>>>- rollback in case of an error
>>>- comprehensive log including records where sync failed
>>>- various other settings
>>>- you can sub-class for whatever extension you see fit
>>>
>>>Conditions:
>>>- 'central' database is behind a Web Application
>>>- each table has a primary or candidate key and 2 normalized fields: 'last update' and 'updated by sync'
>>>- batch execution, not real time: each 'client' runs a program periodically (can be every minute)
>>>
>>>In production since 2009.
>>>
>>>>Hi Guys,
>>>>
>>>>Basically, I am doing a POS app which will be used by a handful of branches and one head office. All will be connected via internet.
>>>>
>>>>We would like for the following to be implemented:
>>>>
>>>>1. Whenever head office say creates, deletes or modifies a new product, it will be propagated to the Products table of each branch.
>>>>
>>>>2. Conversely, branch sales data feeds are pushed to the head office.
>>>>
>>>>3. In the event that internet connection fails during this "synching", how does one know where "we left off" to continue?
>>>>
>>>>Thank you very much in advance for all your efforts!
>>>>
>>>>Long live the Fox!