On some of my pages I have datagrids showing the output from a corresponding stored procedure, which abstracts the record extraction logic away from ASP into the db where it belongs. Paging is set to On in each of the datagrids, but it fails. I click on Next, or the page 3 link on the other web-page, and all I get is refresh of the existing subset of records once past the first page of data. I can't scroll through any of the remaining pages records that the page count displays - eg the Page 8 link refreshes page 2's data. The data is there - I can run the SPs separately in Query Analyzer and get the full set, a few hundred records.

I've checked the documentation; my code and datagrid properties reflect what ASP expects. Could paging be limited by the spec of the server? ASP and SQL server are both running on v low spec PC that acts as my development box - W2K, Pentium PIII, 128MB RAM.

Can anyone suggest a resolution to this paging problem?

Post your code... are you using a SqlDataSource or are you setting the datasource in the codefile?

Jason Hall

Tssk. Paging and page caching are incompatible, which is obvious once you stand back and think about it. I removed the cache directives from the relevant pages, and all is well.