---------------
If for some reason you don't pass the
params in the order specified in the SP then you'll get an error. For some
reason the SP Call made by cfstoredproc seems to pass the values but
not the param names I.E.
sprocName #var1#,#var2#,#var3#. If you miss param 1 or
2 then you get funny results as call will look like sprocName
#var1#,#var3# and Var 3 will be inserted into Param 2. In QA if you use the call
sprocName @p_Var1=#var1#,@p_Var3=#var3#,@p_Var2=#var2# It will work if you
do the equivalent in cfstoredproc and the SP has the variables
declared in order you get odd results.
---------------
Thanks nick, however I have been aware of
the above ever since I started using SPs, thus your example does not need
dbvarname="@P_Var1"
---------------
One last
question, how you are doing debugging, does that give you any more info, like
the offending value, I don't think it does, but I better check?
Not sure I understand the question.
---------------
The issue was CF not giving me enough info
about the error it encountered, i.e. it
returned
[Macromedia][SQLServer JDBC Driver][SQLServer]Error
converting data type varchar to int.
All nice and dandy, but
it doesn't give me much to work with, instead if it said
[Macromedia][SQLServer JDBC Driver][SQLServer]Error
converting data type varchar to int, the offending value is
"im A Varchar Not A
Bit"
I would
have been able to solve the issue much quicker. So my questions was,
whatever you do, will that give you that info in CF?
Cheers,
Taco
Fleur
---You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
