However, if you use the RecordCount or PageCount properties with a server-side cursor, all the records will be read, canceling the performance gain. You must balance having a user interface with more information and richer navigation against having the performance impact of retrieving all your records. When you use a server-side cursor, the CursorType property needs to be adOpenStatic or adOpenKeyset to use paging. Paging is not always an appropriate user interface. Appropriate scenarios might be situations in which users are scanning results from a search engine or browsing a product catalog.
Users can wade through only so much.
Retrieve only the records you need to display. Changes to functionality are easier, and code maintenance is improved. Testing and debugging are also improved, because I can comment and uncomment method calls. This is because ASP reads the entire file into memory when it processes includes, not just what it needs. Conclusion Paging is a common technique that many Web applications use to provide a nice way to browse a large number of records.