Can I just clear a couple of things up here. This is how I understand <cffile action="upload"> if I'm wrong here please correct me.
Having a form with a file field, an enctype of multipart/form-data and a method of post results in the web server (NOT cfserver) recieving a file from the client. This file is then stored as a temporary file in an OS/web server dependant temp directory. This would happen even if the target action of the form is an html file (ie. CF has nothing to do with the process up to this point). The value of the cf variable form.fileFieldName is a string containing the file name (and path?) of this temporary file NOT the contents of the file itself. <cffile action="upload"> is pretty much equivalent to <cffile action="move"> (it just takes the temp file and puts it where you specify in the desintation attribute). The exceptions being you specify the source a little differently, you can control the mime type and you get some handy variables in the file. or cffile. scope. The only things I can see that upload does that you couldn't do any other way is give you the client file name & path and the name of the temporary file that the web server created. So I can't see how: + FileExists(Form.upfile) would fail unless its just the file name & not the path. + Why RAM would really be an issue in the whole operation. If it was it would be the <form> with the file field that was the problem rather than the <cffile action="upload"> What am I missing? IMHO the best solution so far looks like the trailing slash on the destination as Laurent suggested. Cheers Mark ______________ Mark Stanton Web Production Gruden Pty Ltd Tel: 9956 6388 Mob: 0410 458 201 Fax: 9956 8433 www.gruden.com --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
