Frank, Here's my experience:
You must pass the parameters in the same order as they are declared in SQL. The named parameter feature (as I understand it) applies to Oracle - I also believe it to be deprecated in CFMX. The parameters must be in the same order - If you are assigning default values in your SP and you want to simply not pass those parameters at certain times - they must come at the end of the list of declarations and you must not pass in any variables you intend to assign after the first default you want handled. To illustrate: Procedure header.... create procedure foo @a int = 0 @b int = 5 @c int = 3 @d int = 4 WITH RECOMPILE AS....... CF code..... <cfprocparam type="in" cfsqltype="CF_SQL_INTEGER" dvbvarname="@a" value="99"> <cfprocparam type="in" cfsqltype="CF_SQL_INTEGER" dvbvarname="@b" value="10"> <cfprocparam type="in" cfsqltype="CF_SQL_INTEGER" dvbvarname="@d" value="110"> In this case, the value of the variable "@c" will end up being 110 and the value of "@d" will default to 4. That's been my experience. Futzing with the order of declarations and the <cfprocparam> has been the only solution we have found. Mark -----Original Message----- From: Frank Mamone [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 1:12 PM To: CF-Talk Subject: Stored Procedure Problem Hi, I'm trying to call a an stored procedure to MS SQL 2000 using Named notation for the parameters. There's always an error, so we did a trace and found that the parameter names are not passed. Any ideas? Frank Mamone ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
