I could be wrong about this, but from what I have read, you cannot do what you are asking using Access. Access is not a true client/ server database, but only acts like one in the fact that you can have your data stored in a remote location, BUT all of the transaction processing still takes place on the user's machine. A TRUE client/server db would do what you are asking, that is, process the query on the server and return only the results to the client. As a result, depending on the size of your d/b, the number of users, etc, it is possible to generate large volumes of network traffic using Access. For true client/server transaction processing, which is what I think you are talking about, you would have to use a different database program with a server... something like SQL server.
This may not be feasible in your situation, but one thing you could try if you have an intranet is to use HTML as the interface to your data instead of Access. I can't give you advice on how to do this b/c I haven't tried it myself. I do know you will need a copy of Microsoft Personal Web Server (PWS) which is a free download from their site. Look under NT 4.0 Option Pack.
If you do it right, by using your intranet & PWS, you can essentially set up a true client/server system and possibly be able to eliminate some of the network traffic. Again, I am not sure about this and it also might NOT be feasible for your circumstances.
That's my $.02!
I would be interested to hear what other people have to say about this.
Jamie
