I'd say that's a slightly kludgy hack that I only mention because the 'right' solution was proposed and overruled. You're implicitly coercing the numeric result returned by 'len' into a boolean value, which works, because of the typeless nature of CF. By using a numeric comparison that returns boolean, you avoid implicit coercion, which makes the code easier to read. It's a subtle difference, but it's worth that extra keystroke, IMHO.
cheers, barneyb On 4/27/05, Bryan Stevenson <[EMAIL PROTECTED]> wrote: > >> > >> This is also the technique I use. > > > > Of course I put "EQ 0" at the end there. > > as Dave W corrected me yesterday : > null="#YesNoFormat(NOT Len(Trim(FORM.txtFirstName))#"> > > I like the use of NOT instead of EQ 0 ...1 less keystroke ;-) > > Bryan Stevenson B.Comm. -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:204711 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
