I&#039m slightly confused here. I&#039ve read several articles saying that the best way to page through a recordset is to use a stored procedure because if you don&#039t, the contents of the entire table will be sent from the database server to the webserver on each request. <BR>This seems logical, but a friend told me the other day that you don&#039t need stored procedures. All you need to do is to set the CacheSize-property of the recordset, thus avoiding the problem.<BR>What is the way to go? I understand that stored procedures have other advantages, but it seems so much easier to just handle the paging on the webserver.