This content has been marked as final. Show 3 replies
> There is a dbVarName attribute but it hasn’t worked since the pre-MX days even
> though it is still referred to in certain places in the docs.
IIRC dbVarName did work in 7.0.2. Though this link suggests they may have reversed this behavior in CF8. I'm not using CF8 so I can't test it.
Thank you for your reply. Yes, I did see that link in my search but since dbVarName isn't officially noted in the docs I'm hesitant to use it. Furthermore, we use Microsoft's Java ODBC driver. It doesn't seem to play well with the dbVarName attribute for whatever reason. It would be best if <cfquery> simply worked for stored procedures like it used to in CF7. Unless this changes I don't see how my company could ever upgrade to CF8.
I get correct results from a similar stored procedure with CF8 using either the CF8-supplied SQLServer driver or the Microsoft v1.1 JDBC driver from
It works OK with SQLServer 2000 and with SQLServer 2005.
Since you are not getting any error, it doesn't seem that you need to use dbVarName.
Maybe you should try it with a test procedure which just returns the arguments to see what is going on.