One convenient aspect of CF regarding repetivitely used queries are cached queries, which you lose if you employ bind parameters via CFQUERYPARAM or stored procs called via the CFSTOREDPROC tag.
So, the question becomes how to achieve re-use of query resultsets if your underlying database access approach can't take advantage of CF's inherent query caching. Obviously these queries could be stored in the application scope, and updated should the underlying data change. I suppose you'd want to keep them in a structure encapsulated within a CFC and develop a naming convention to refer to them. I've been giving this some thought as to approaches, and I thought I'd post and see what others have done. Jeff Battershall Application Development Consultant Dow Jones Indexes [EMAIL PROTECTED] (609) 520-5637 (p) (484) 477-9900 (c) ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
