Because CFImage isn't supposed to be used as a file system manipulation? Even functions like fileMove() doesn't even have one. Only one that I'm aware that has a nameconflict attribute is CFFile action="upload." There's a reason why we have functions like fileExists().
On Nov 7, 2007 1:14 PM, Rick Faircloth <[EMAIL PROTECTED]> wrote: > One thing I did notice is that the cfimage tag doesn't have a > "nameconflict" option. > It seems it really needs one. Any reason why it wouldn't have one? > > Rick > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Get the answers you are looking for on the ColdFusion Labs Forum direct from active programmers and developers. http://www.adobe.com/cfusion/webforums/forum/categories.cfm?forumid-72&catid=648 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:292860 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
