When you say you "modified" the stored proc and "executed it" do you mean you executed an ALTER statement on the proc?
If you re-open the proc and the new parameter shows up, then I'm sure it is saved. Did you add the new parameter to the end of the list of params? Since dbvarname is largely ignored, the params are passed by position. Something quite possibly could be cached. Check your pooled statements setting in your datasource. I'm not sure if there is a way to clear those out easily with out restarting CF, SQL, or just going in and killing all the SPIDS that represent connections from your CF server. If it's a dev server, just bounce CF I guess. Before you do that though, double check the data source you are using and make sure that you are calling the procedure you think you are and not one in a different database/server/name/etc. ~Brad -------- Original Message -------- Subject: stored procedures From: "Chad Gray" <cg...@careyweb.com> Date: Wed, November 18, 2009 10:43 am To: cf-talk <cf-talk@houseoffusion.com> I am trying to add a field to a stored procedure. I "modified" the stored proc in SQL Studio and executed it. It appears to have "saved" the changes. Now I added <cfprocparam dbvarname="@PromoCode" value="#session.promocode#" cfsqltype="cf_sql_varchar"> to my CFStoredProc tag. I get the error "Procedure or function I_Orders has too many arguments specified." Did I not edit the stored procedure right? Is it cached somewhere? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:328494 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
