>> if you look at the above code you'll see that the CFPROCPARAM
>> is missing the DBVARNAME parameter. I don't know how it got
>> passed the CFDebugger into our production environment but it did.
>
>It's been a while since I've had to worry about CF 5, but I don't think
>that
>the DBVARNAME attribute is always required in 5. I know that it's not
>supported at all in later releases. In the absence of a name, positional
>notation is generally used.

The DBVARNAME should not have ever been required. 

I remember being very disappointed that MS-SQL did not support the DBVARNAME
when the stored proc tags first came out. I remember being stumped on why my
code broken when I re-ordered some of the <cfprocparam /> tags. I thought
the DBVARNAME attribute was enough and that order would be irrelevant.

-Dan


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four 
times a year.
http://www.fusionauthority.com/quarterly

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:258940
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to