Brad, Thanks for the helpful suggestions.
In terms of numbers of inserts, well it's an insert statement within a cursor loop. There's 305 records being added so it loops 305 times and does an insert. As I mentioned in my last post. When I take my execution page out of the pseudo-fusebox app and run it separately, it works perfectly each time. So what I did was add an application counter in the original app on the query page, and yes it was calling it multiple times for no reason. So fine, I figured, I'd just put an IF statement around the stored proc. However, what I found was that the error was happening even if my counter was 1 or 0, meaning that the first time through, it was still getting a primary key constraint error. So, I have determined that internally, either the CF server or the JDBC driver or some way in which the cfstoredproc is being handled, is executing the stored procedure in SQL multiple times. Even if I have a SQL Profiler, it's not going to help in telling me how to stop that. And if that is true, then how come ColdFusion handles it differently when I pull that CF page out of that app, and run it by itself? Ali ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:329648 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
