>>>>Thanks Larry but I can't find a company named SilverFox in internet. Could you tell me the full name and URL of it?
>>>

>>
>>You might want to look at Reachout 7 by Stac. (www.stac.com)
>>This runs under Win95 and allows script files to be constructed which run remote programs at the remote end including transferring files. It has a "synchronize folder" routine that "updates" the remote directory for the contents of the host directory it is working with, transferring only "new" information. Also, the speeds are enhanced by only transferring the updated information in a file, not the entire file. I am able to update a remote computer with a 30mb database daily within about 20 minutes. Works pretty slick. It also records a log so you can follow up on why a connection was not made at the "off hours" setting the next day.
>>
>>HTH,
>>Bill
>
>Yes but it cannot update a dbf that has input coming from multiple locations, can it? If Yung is looking to have a master (home office) dbf which combines information from multiple sites (branches), then the updates it will need to be done programatically. Changed records for a dbf need to have its status coded (as an update, addition or deletion), then the transfer utility (SilverFox or ReachOut or whatever) can move the files. Once the files are at the target location, then the changes can be added to the local dbf based on the record status code.
>
>The management of the two way transfers is the trick. A great deal of time is involved in ensuring data integrity between the home and branch sites.

We just completed a similar set of utilities that, along with Reachout, do that. New records from a remote site are exported to a series of update tables which are then sent by Reachout to the remote site. After transferring the update files, Reachout runs a VFP routine that appends these to the host database. Then the host database constructs an update file for the remote site, which again, is transferred by Reachout and Reachout executes a routine at the remote site which conforms the remote data to the host. The routines run by Reachout at each end are VFP routines. There is a status file which then reports the progress, success or failure of the periodic transfer routines. Part of the VFP routines include making backups of the tables prior to update so that an aborted update will not prevent a successful recovery.

If I read your concern properly, I still think that this combo does it. The advantage of Reachout in this instance is not only that the script can be created to run remote programs but that the file tranfer algorithms are so much more efficient.

Bill