> I won't run into a valid issue if the file is never uploaded 
> to the server in the first place. Basically the user submits 
> the file, before the <cffile> action I check the file name 
> and see if it already exists in the database.
> If it does, then I return the error. If it doesn't exist, 
> then go and perform the <cffile> action.

Well, by the time CFFILE runs, the file has already been uploaded to the
server. CFFILE just takes the uploaded file out of a temp directory and puts
it where you tell it to.

> There's a way to do this in ASP.net by checking against the 
> name of the file field and the http header to grab the file 
> name. I believe the control is browser.httpheader {form.fieldname}

This basically works the same way, if I understand correctly. The file
itself is embedded in the HTTP POST response made by the browser. By the
time your server receives that response in its entirety, your server has the
file.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/

Fig Leaf Training: Adobe/Google/Paperthin Certified Partners
http://training.figleaf.com/

WebManiacs 2008: the ultimate conference for CF/Flex/AIR developers!
http://www.webmaniacsconference.com/

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to 
date
Get the Free Trial
http://ad.doubleclick.net/clk;160198600;22374440;w

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:298205
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to