>> Does this means if Im in a Lan an I have a backgroud Serversync proc then I must assert it runs in one only pc?
no, it's welcome to run on multiple PC's.
it only "has" to run on 1, but extras should be no problem.
>>>The sync procedure can be triggered by a timer (every few minutes or so). This is in the template, if I want to call the sync myself which value must I use? zero?
If you plan to alter the way the sync works, then I suggest you spend some time really understanding how it works, and what the impact of your changes will be. By all means makes changes to the plan, but then don't come crying to me when it doesn't work well
- Data replication is complicated and it's designed the way it is for a reason.
>> I mean if I will call the proc by code and I dont want it to sync every xxx secs.
Examine in the code, see what the timer is doing, and go from there.
Bear in mind that more infrequent updates will lead to bigger syncs, and obviously more data is "inaccurate" for longer periods of time.
>> or it could be triggered by NetRefresh so that it synchronizes after every write.
>> how to do this?
>> how to use NetRefresh with sync?
That's probably a topic for another day. But short answer is that NetRefresh sends an event to your program, you could use that event to trigger a sync.
cheers
Bruce