Access and SQL Server

[petermeachem]

My front end is Access 97 and the backend is SQL Server 7.
The user enters a date and a coupe of other things and the form displays a list of editable records. I currently have attached tables and am doing me.recordsource = "SELECT etc".
This works fine, but I am informed could be improved if the query was run on the server. I know how to write a script on the server with parameters. The problem is I can't figure out how to persuade the Access form to take any notice of it.
a) Is this worth doing from a performance point of view?
b) How do I do it?

I have SQL on a very slow old pc here and the customer has a stonkingly fast Compaq, but as far as I can see the rate that the Access form updates is much the same in both cases. This means I suppose that either the network, or Access is causing a bottleneck. As far as I can see, only about 60kb is being read across the network per query, so it looks like Access.
Any help appreciated!

 

[petermeachem]

The plot thickens.
I knocked up a vb7 programme that replicates one of the Access forms. The display in the (Janus) grid on vb is virtually instant whereas the Access one draws it in line by line. The amount of data transferred is however exactly the same in both cases. ( I am looking at 'non paged read bytes requested' in the NT Diagnostics prog. I hope this is a reasonable measure)

So the question is why does Access appear to look so dreadfully slow when the back end is SQL when the network traffic is the same as VB, and what can I do about it. I'd like to stick with Access and SQL if possible as it's so easy.

 

[petermeachem]

I meant vb6!