As long as the data is pretty static, you could break it apart based off of some unique identifier.
For example: SELECT ..... FROM ..... WHERE recordID > #lastIDSelected# ORDER BY recordID Each successive query would be faster. This is not a perfect solution, but it may give you an idea on how to best solve it for your purposes. M!ke On 8/30/05, Snake <[EMAIL PROTECTED]> wrote: > Like pretty much everyone else, I have always used the following > method for paging through result sets, > > <cfoutput query="whatever" startfrom="#startfrom#" > maxrows="#maxrows#"> > > And altering those variables to allow 200 records per page or > whatever, > > But this means querying ALL records form the database each time, which > can be very excessive when your dealing with a very large database. > Has anyone come up with a good solution of only querying the records > you actually need (rows 40 -59 for example). > > > Russ > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:216903 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
