Thanks for the response, Dave, but that logic doesn't make sense to me, and I'm hoping you can help explain as to why that should work (I got a massive puking error when I attempted it, too).
> > <ul> > > <cfoutput query="qSpecific"> > > <cfif #qSpecific.RecordCount# GT 0> > > ... > > You should put your CFIF around your CFOUTPUT, rather than > the other way around. If there are no records, the CFOUTPUT > will loop zero times, so your CFIF never gets to do anything. Wouldn't I want the query to happen first? That way the record count would actually have something to go against? By placing my CFIF around the output, it would seem as if I'd never have the chance to run the query first, and then have something to count against. Since I'm saying "if there's more than zero records, which I should know the instant I run the query, then go ahead and display those records, otherwise, if there's not more than zero, display 'there are no records'", that CFIF on the outside seems to (to me) make it fail. Thanks, Russ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com
