> Er, isn't it nameconflict="unique" which causes the above to happen? i.e.
> when a file name conflict occurs the server has been instructed
> to generate an *unique* filename, which could be different to the uploaded
filename.
Well.... "<CFMAIL ...
mimeattach="e:\inetpub\hostroot\aaintl.com\MailFiles\#File.ServerFile#" is
working great for me.
The file is being saved on the server with the ORIGINAL filename..not a
different name.
So, from my understanding of how this works comes a different
question....what if two different users on the site happen to hit the
"SUBMIT" button on the form at the same time? Is it possible for the
attachments to get confused as to which email they're supposed to be with?
What if the remote possibility of two users at the same time with the same
file name? What the heck happens then? If this is a possibility, what's the
best way to prevent this before it CAN happen?
I obviously don't want to create something that looks like it's working
great now, but later when 50 people are using the forms (very remote chance)
at the same time I run into problems.
Les Mizzell
***********
Who needs Intel?
Athlon Inside!!!
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
