>I'm afraid you've lost me - I don't see how I could apply stored procedures to the second example in any way and get any sort of reduced network traffic. Or maybe I'm misinterpreting. In a client server app using a back end, I'm using remote views so the query processing happens at the server and only the result set is sent back. If I'm not using a back end, I'm using local views, and the query processing happens locally, pulling all that index data over the wire. Even if I did use a stored procedure somehow, that procedure is still executing on my local machine, and would need to pull index data over the wire.


I ment an MS SQL stored procedure. When ever you are processing many records sequentially in a client server environment, the best answer is to have the process happen on the back end. (stored procedure)...

Since the stored procedure runs on the back end server machine, those thousands of records are not pulled across the network.

BOb