On 5/30/05, Jared Rypka-Hauer - CMG, LLC <[EMAIL PROTECTED]> wrote: > And cfquery... since it creates a metadata container when you execute a > query. > > And your query results. > > cffile (var cffile and variable both), cfhttp, cfparam (whatever the name > attribute is), cfpop, cfsavecontent, cfdirectory (whatever the name > attribute is)... basically anything that leaves data behind, in any and/or > all contingencies. Depending on the situation you may even need to var the > form, cgi, and/or url structs.
If you're using CFMX 7, you can simply use the new result= attribute on these tags and then you can specify a local (var) variable into which the tag should write its data (instead of the default variable, named for the tag itself - not all of which you can var declare!). -- Sean A Corfield -- http://corfield.org/ Team Fusebox -- http://fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
