Hi Joe,

>With our corporate FoxPro app, the DB resides on the server, and many PC's access the DB from our FoxPro app that is located on each PC.
>
>When each PC does a query of the DB, the PC gets all the table data from the server DB, and the PC does all the processing needed itself, then displays the results... correct?

That is an over simplification, but for the sake of argument... yes. For any given task, as I understand it, the indexes travel across the network wire, and then (using index information) the appropriate records are pulled across the wire. This of course assumes that you are doing a task that does not require the entire data table. Also, once the indexes are at the local PC, VFP make smart use of caching so that future data reads/writes may not need to retreive additional index info.



>Is there a way to have the server side do the SQL processing? And then the server would send the results to the PC?

Not without a lot of work either writing a VFP backend, or using a database like SQL Server, Oracle, MySQL, Postgres QL, etc. Any choice you make here is likely to cause some rewriting of logic.



>
>And if so, would it be quicker for us?

It depends. If your bottleneck is network traffic, then yes. It could make a noticeable difference. But, if your bottleneck is somewhere else, you may not notice any performance increase.

Guy