Eric,

First of all, let's get our terms straight. When you say client/server do you mean that the executable is on the clients and the VFP database is on the server? If so, that's not technically client/server (even thought there's are clients and a server). If you're using a database server like SQL Server or Oracle, that's client/server.

If you're using a VFP database you'll need to write programs to do the updating and conflict handling. You could use off-line views to make this a bit easier, but there's still a fair amount of work involved.

If you have a true client/server environment you could use your database server's replication features. This would probably work well with Oracle or SQL Server 7 (SQL Server 6.5 only supports one way replication).

>Our company has been using a database developed with VFP 3.0 for over a year now and have operated it on a typical client/server network. Now, however, we are expanding our operations to include two branch offices that are out of state. Keeping in mind that we want to have daily updates of changes made to the database from those branch offices and will also continue using and inputting on the database from our main office, what is the best way to set up these transfers? Thanks in advance for any advice.