monitoring data transfer from server to client

I develop a database application using MSDE, ADO2.8, VB6. This application will be used by a small group of users (no more than 3-4), a couple of which will be accessing the server through a low-bandwidth line (128kbps).

Is there a way to presume the bandwidth usage of my application before actually installing it to the network?

Is there a way to know the amount of data being transferred from server to client during a query execution?

Ideally, is there a way to simulate a low-bandwidth connection between Server and Client, using just my PC? (So that I can optimise my queries, adopt a deferent approach, or even suggest a hardware upgrade)

thanks in advance

BTW this is my first post :o

Is there a way to presume the bandwidth usage of my application before actually installing it to the network?

Is there a way to know the amount of data being transferred from server to client during a query execution?

Hmmm..not sure what your after. In terms of speed of execution and sending queries between the client and the server, typically running your query with a server side cursor will be quicker and require less overall overhead. When you say "know the amount of data being transferred" you are really going to have to be more specific. Do you mean the physical number of records processed, the amount of memory being used to execute the query or procedure..the physical number of bits processed and scanned, etc..not sure what you are trying to accomplish.

Thanks for your reply MKoslof

I 've already used a server side cursor, and I store small lookup tables localy in Collections during startup.
What I really need to know is the physical number of bits "travelling" through the network when the client executes a row-returning query. Does the size of the recodset (saved with a param adPersistADTG) indicate the quantity I 'm after?

Not really :). I don't think you can get this information from VB. VB doesn't really have access to this information..SQL Server basically protects this information and I don't think the COM layer can report this.

Off hand, I don't think you can return this information. The size of the recordset will not give you an "accurate" count of the amount of bits and memory being processed as the query is being run.