>In this case, the data would still need to be sent from the server at some point. An optimized C/S application would limit the number returned at any one time (i.e. say, 100 records at a time) when you reach that limit, the next batch is fetched. You should be able to do this via local views as well, but like I said, I want to double check that.

Thanks for the info. How would one set up a grid based on a remote view that fetched only 100 records at a time. If you scrolled down past the 100 would the user then have to hit a key saying view next 100 etc. If so that is really not the ideal interface irregardless of the amount of network traffic. Also how would you handle seeks? If you only fetch 100 at a time will the seek bypass this and find the right record and fetch the next 100 after that automatically or do you have to code for this.
Sorry for all the questions but I haven't worked with remote views before and am still unsure of how the fetching thing works.

TIA