The issue was not whether the overwrite was happening -- it definitely was -- the new image was written. There was no ftp involved -- this was all cffile from a form post.
What I noted was that the original file -- the one being overwritten (with the same name, but different case), did not use the explicit case specified in the cfimage tag. Added interesting note is that the file is being resized as well. While this isn't really an issue for us on a windows server, if we were to ever move this image storage to, say, a linux server, this would be a problem, in that what we've stored in the DB as the filename would not match the filename on disk. We're expecting a lower-case image name since that's what we're passing to cfimage, so that's what we're storing in the DB. Cheers, Kris > One of us apparently misunderstood the OP's issue. :-) I thought he said > > that the file was being renamed, as opposed to overwritten. You are > stating > > that it is indeed being overwritten. I'm not sure which the case is, but > as > > Robert pointed out, it might be a file lock issue. <shrug> > > No, it's not a file lock issue. In Windows, when you overwrite a file, > it doesn't matter what case you specified - the filesystem performs a > case-insensitive match, and overwrites whatever's there. If you want > different behavior, you need a case-sensitive filesystem. > > Dave Watts, CTO, Fig Leaf Software > <http://www.figleaf.com/> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:340952 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
