Lloyd R. Prentice wrote:
  Hi D. R.,
 D R Holsbeck wrote:
 On Sat, 2002-10-12 at 13:14, Patrick Shirkey
wrote:
 >Cold Fusion deals with files through the
<CFFILE ACTION="someAction"> tag,
>where someAction = Move|Rename|Copy|Delete|Read|Write.
>
>An example of the Read action would be:
>
><CFFILE ACTION="Read"
>FILE="file_name"
>VARIABLE="var_name">
>
>var_name is the name of the CF variable that will contain the file once it's read.
>
>Is this any more help?
not really. There is a link on a page which points to this address:
/launch.cfm?mixid=5014 
Find the file that is pointed at by /launch.cfm. In other words
launch.cfm should include something similar to
 ><CFFILE ACTION="Read"
>FILE="file_name"
>VARIABLE="var_name">
> 
as pointed out by Patrick. 
 The problem is, as I pointed out in an earlier post, the CFFILE tag is processed on the
 server side; it's not accessible on the client side. If Patrick has access to the
server
 and *.cfm source, on the other hand, he may have hope.
 
 Well I got close by scrounging around in the source for a few of the
 pages but no success yet. It's a pity that the format causes problems
 for Linux apps. It seems to be used in a lot of good sites that I have
 found over these past couple of days.
 --
 Patrick Shirkey - Boost Hardware Ltd.
 For the discerning hardware connoisseur
 
 - The Linux Audio Users guide
 ========================================
 "Um...symbol_get and symbol_put... They're
 kindof like does anyone remember like get_symbol
 and put_symbol I think we used to have..."
 - Rusty Russell in his talk on the module subsystem