I'm guessing this sp was working in MX 2 days ago and so you're ruling out
an upgrade as being the reason for it's not working?

In CF 5 you would get this error if you left out a parameter prior to
@ccAuthCode expecting the db to be able to use the default value defined in
the stored procedure -- in which case, ColdFusion Server is ignoring the
fact that you have named your variable @ccAuthCode in your <cfqueryparam> (
this is apparently not a "bug" although I'm not aware that it's documented
either ) and simply crammed it into the previous, omitted parameter, in
spite of the name and / or any data type specifications. Unfortunately, if
you want to omit a parameter in CF and allow the stored procedure to use the
default value, your default parameter must be at the end of the list of
parameters. All other parameters must be in the same order they are
specified in the stored procedure definition.


hth

S. Isaac Dealey
Certified Advanced ColdFusion 5 Developer

www.turnkey.to
954-776-0046

> Are you supplying the variables in the right order?
> Your queryparams need to be in the same order as they are declared in the
> SP.

> Ade

> -----Original Message-----
> From: Chad [mailto:[EMAIL PROTECTED]]
> Sent: 26 September 2002 17:33
> To: CF-Talk
> Subject: Stored procedure error


> Error Executing Database Query.
> [Macromedia][SQLServer JDBC Driver][SQLServer]Procedure 'I_CustInfo'
> expects parameter '@ccAuthCode', which was not supplied.

> We are getting this error and yes the variable ccAuthCode is defined.

> Is anyone having trouble with stored procedures and MX because this
> stored procedure was working 2 day ago.


______________________________________________________________________
Signup for the Fusion Authority news alert and keep up with the latest news in 
ColdFusion and related topics. http://www.fusionauthority.com/signup.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

Reply via email to