I've built something like this myself and as Ian says its all about your validation routine. You run it, you test each field with everything you can throw at it (in my case regexes are my friend) and you tell the uploader of problems with the upload operation. If something gets past the regexes and a sql write fails the reason is logged separately. Also you may or may not want to skip over error records and continue with the good ones, or fail the whole upload depending on your business rules. I use the intermediate temp table concept as well to keep the upload the heck away from a live db until its been fully vetted.
Its all possible with CF. You just have to code it. -- [EMAIL PROTECTED] Janitor, The Robertson Team mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:305122 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
