After setting up a slave server you can ndo simple tests to verify the function.

In this a animated GIF I have two appliactions running a UI that has PeriodicAction that does a simple update of an attribute - and then a refresh and a save.

I also run the prototyper as a 3:th app against the Slave server.

Notice that the lower of the 3 is a bit choppier when getting data refresh for the first two rows that are updated in the Master db.

This because the transport via the MDrivenServerSynk.

This is the expected behavior of a Slave server.

The PeriodicAction looks like this:

vCurrent_Details.Company.Name:=vCurrent_Details.Company.Name+'x'; 
if vCurrent_Details.Company.Name->length>10 then  
  vCurrent_Details.Company.Name:='C' 
else  
  '' 
endif; 
selfVM.Refresh; 
selfVM.Save