>What is wrong here?
>
>Have data (FoxPro tables) on a remote server and when executing a SQL through a .EXE ( using a stored procedure ) the resultant is 50 records equaling about a file size of 12K dbf yet we see over 25 megs. coming over the network? It wasn't until we put a sniffer on the network because of slow performance that this came to view. Comparing this to execting a SQL from the application showed no detecable difference. I was always under the impression that using stored proceedures only the resultant record set would be delivered and for that manner the same when execting a SQL from the client side.
For a start, read my FAQ #8109, which has some ideas on query optimization. Also, post the actual query statement(s) here, so that we can help you.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
