>Anybody ever tried to synch up VFP 7.0 data with SQL server 2000?
>
>We have a client, and they want to synch up a bunch of our VFP tables (living in New York City) with their SQL Server in L.A. over the internet. This is to accomplish a Data Warehouse task.
>
>Anyone ever had any success with this? We already audit Inserts, Updates & Deletions on the tables they want, via triggers. This information is stored in a master audit table, with the primary key, the table name and the field(s) that have been changed. The master audit table also has the type of change (I/U/D).
>
>The problem they are having is with remotely connecting to our VFP tables and querying them. Several tables are rather large (in the 1.0 to 1.6 GB range). Their .CDX's are also pretty big. They are trying to run SWL queries, and are having bad results as far as time goes; they say it's way too SLOW.
>
>Any thoughts at all? We don't even know where to start.

All SQL statements (Selects, Inserts, Updates and Deletes) should be executed locally (in NY): the LA office should always INSERT its SQL statements into an NY based table that is being watched by an NY based process. Let's call this table Inbound.DBF. Results of SQL SELECT statements might best be returned as zipped DBF's, XML or comma delimited lists.

I'm assuming that SQL Server 2000 has the flexibility to receive and handle a compressed data set.

The process in NY that monitors Inbound.DBF can use polling (check every second or so) to see if the RecCount() has increased. Or if you want sub one second responses (seems unlikely between NY and LA) you could use Win32 API FileEventNotification.