Ooops sorry, yeah you're using AS 2.0 syntax. So it is 2.0. However, there are
other ways of handling the remoting code. In the Flash dictionary, in the
remoting section, there is a very detailed example of how to create remoting
code with CF. It includes examples for result events and fault events. I highly
recommend you look at that when you have a chance. It's just a different way
of handling it, and I like it. I'm going to rewrite that code I gave you.
I'll try to get it right this time. One thing I notice is you're not setting
enough variables for the cfdocument tag. By default that tag is set to build a
document right into the browser. I don't think that will work with remoting the
way I suggested or with your example either. There are a couple of way you
can do this. One way would be not to even use remoting. Just have link that
goes right to your original example. EX: getURL('myCFC.cfc?method=createPDF',
'_blank'); EX #2, This would require a little expirementation since i haven't
used this document building code before: <cfcomponent> <!--- Remoting Call
---> <cffunction name='myRemoting' access='remote' returntype='boolean'
hint='I am the remoting function'> <cfset pdfStatus = createPDF() />
<cfreturn pdfStatus /> </cffunction> <!--- Create PDF ---> <cffunction
name='createPDF' access='private' returntype='any' output='true' hint='I
generate a flashpaper'> <cftry> <cfdocument format='flashpaper'
filename=''>Hello World!!!</cfdocument> <cfset result = true /> <cfcatch
type='any'> <cfset result = false /> </cfcatch> </cftry> <cfreturn
result /> </cffunction> </cfcomponent> FYI, I have written a tag or rather
a set of code that aides in document building. It's called DynamicFiles. You
can see it at
www.cftags.net At some point I may roll this cfdocument code
into this. My tag kind of helps pick up where CF leaves off. MM should have
built additional file type genertation in the cfdocument tag. Such as word
docs.