Caching the query for "paging", ie next 10 records, previous 10 records, firs page, last page, is a great idea.
But take this into account first: How "dynamic" will the list be - if not altogether dynamic - great. Otherwise - if the database data is changed, force a database "refresh" to the same scope as your cached query to ensure the end user is seeing the up-to-date information. Apart from that this method can really help your application performance, as long as you respect the amount of memory you server has and the limit of (100 cached queries I believe - limited by the servers memory - 1 cached query could kill it) that CF has for this. --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
