> Basically, if I'm writing to the "badFiles" location, I have almost > invariably broken out of a <cfloop file="whatever"> loop before > reaching the end of the file (using <cfbreak>). Is it possible that > ColdFusion still has a lock on the file and, therefore, can't delete > it? (I'm thinking this may be the case, because right now I can't > manually delete that file from the source folder, either).
Yes, I think that's very likely. > Assuming that's the case, any ideas on how to get around it? Because > this is a process we don't want to bog down unnecessarily, I'd rather > not read the whole file in (the old way of looping over a file) or > loop over the entire file if I don't have to. You could copy the file, then schedule a task to delete it in the future. Or, you could see how long file locks exist in your OS and see if you can make that shorter. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsi ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:329697 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
