>>James,
>>
>>This doesn't make sense to me. Whether you use the VFP ODBC Driver or Native VFP the data engine is the same, and it runs on the work statation, so wouldn't network traffic be the same? Have you tested this with a netowrk sniffer?
>>
>>BOb
>
>Hi Bob,
>
>About a year ago I worked for a company that had one of the worst netowrds I'd ever seen. The application we wrote just choked the network completely out and the application crawled. On top of it, a large portion of our users were accessing the app over CITIRX and the bandwidth there was also too low.
>
>A different application was using SQL Server to accomplish almost the same thing on pretty much the same network (different domain). Through experimentation we found that we could get a significant performance gain by accessing our own data through remote views and ODBC.
>
>Although the engine is local, ODBC is pulling only the data it need from the server. I don't know enough about the engine to explain why this was true, but that's the results we got.

James,

But, you are talking about SQL Server... which accepts the command, and just sends back a result set, which you talk to through the ODBC driver.

But, with VFP tables the ODBC driver is also the data engine.

BOb