I have no reason for it but this is the one thing I tend to never prefix a
scope before when referencing.  I often think about it but just never have
adjusted my ways.  So if I have <cfquery name="qryGetData"> ... I do not do
<cfoutput>#Variables.qryGetData.ColumnName#</cfoutput> instead I do
<cfoutput>#qryGetData.ColumnName#</cfoutput>  I like to think of myself as a
scoping Nazi but this one case I slack on.

On Thu, May 19, 2011 at 10:29 AM, Steve 'Cutter' Blades <
cold.fus...@cutterscrossing.com> wrote:

>
> (BTW,
> you should also scope query names). .
>
> Steve 'Cutter' Blades
> Adobe Community Professional
> Adobe Certified Expert
> Advanced Macromedia ColdFusion MX 7 Developer
> ____________
> http://blog.cutterscrossing.com
>
>
> Co-Author "Learning Ext JS 3.2" Packt Publishing 2010
>
> https://www.packtpub.com/learning-ext-js-3-2-for-building-dynamic-desktop-style-user-interfaces/book
>
> "The best way to predict the future is to help create it"
>
>
-- 
Aaron Rouse
http://www.happyhacker.com/


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344748
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to