Thank you for pointing that out. It looks like I missed that. So basically, the order of cfprocparams being passed is all that matters and no parameter can be missed when writing cfprocparam tags.
Is there any performance (i.e. binding) savings to using the CFSTOREDPROC tag vs. a CFQUERY with CFQUERYPARAMs? Is the CFSTOREDPROC call as efficient? Better? What's the advantage? Anyone from MM want to comment? Thanks > -----Original Message----- > From: Tangorre, Michael [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 21, 2004 12:48 PM > To: CF-Talk > Subject: RE: CFStoredProc bug? > > > From: Michael Dinowitz [mailto:[EMAIL PROTECTED] > > Yep. > > > > <cfprocparam type="In" cfsqltype="CF_SQL_INTEGER" dbvarname="Order_ID" > > value="#Arguments.Order_ID#" null="no"> > > > > This binds to the Order_ID inside the SP which is defined > > (inside) as @Order_ID. The reason for the @ inside is to show > > it's a SQL variable. > > The dbvarname attribute is no longer used in CFMX: "it is now ignored > for all drivers.... ColdFusion MX does not support named parameters". > > Mike > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - New Atlanta http://www.newatlanta.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188413 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
