Never mind.. I was editing the wrong stored procedure. There was one on another table that was accessing the table I was working on.
So basically there were two stored procs. One on table1 that was accessing table2. And one on table2 that was accessing table2. I changed both stored procs and now it is working. Very confusing to have a stored proc on a table that is modifying another table. Thanks for the input though! Chad > -----Original Message----- > From: b...@bradwood.com [mailto:b...@bradwood.com] > Sent: Wednesday, November 18, 2009 12:26 PM > To: cf-talk > Subject: RE: stored procedures > > > 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:328495 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
