Since VFP database is an ISAM db the ODBC driver still uses the files to access the data. When an sql select is made the odbc driver still uses the cdx if one exists to gather the data. The entire index will be sent to the client and the client machine then process the index an goes back across the network for the results. This is no different than native access. Additionally my time trials show that using odbc to access VFP data from a vfp client is slightly slower than native access. In my mind the only reason to use odbc in this scenario is to ensure database scalability. In other words, upsizing to SQL without having to change the front-end code.

Steve,
I agree with the other messages that HTML/XML should be your eventual goal, but I'm curious about your statement that the traffic is the same with ODBC. If you use remote views (not local views) isn't the traffic limited to JUST the data in the views? Just as it is with SQL-Server?

Barbara

>I have found that the VFP ODBC Driver creates the same connection to native tables that a regular client connection does and therefore creates the same amount of network traffic. I think the trick here is to get the data localy via a web server and package the data as xml or http and send this packet across the WAN. It looks like Web Connection will do this for us.
>
>Thanks again for you suggestion.