CF's validation to happen when the user leaves the field, rather than waiting until they submit the form. That's now an option, as of CF 7, though many missed the change.
Very well said Charlie. I read about _required feature and it stuck in my mind that I decided if I cannot come up with something feasible, I would stick to _required feature to get things moving. Thats why I suggested CF Server Validation which would avoid popups. You are absolutely *spot on* about using the new feature ValidateAt which supports all 3 levels of validation. In this case, I guess OnServer, OnBlur make lot of sense. On the side note, I didnt know you are on this group as well. ;-) Thanks mate for the tip. It surely might have slipped from many people. <Ajas Mohammed /> http://ajashadi.blogspot.com We cannot become what we need to be, remaining what we are. No matter what, find a way. Because thats what winners do. You can't improve what you don't measure. Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives. On Wed, Jan 28, 2009 at 5:08 PM, charlie arehart <[email protected] > wrote: > Well, if the user doesn't learn their lesson about whatever is failing > their attempted data entry after the first couple of prompts, I'd think > they'd have bigger challenges in their life. ;-} > > > > Seriously, while I think we would all discourage use of any form with 200 > inputs (and the ideas recommended to consider a multi-page or multi-tab > interface were again good ones), I'd think that getting prompted at each > entry would be MORE effective in a form with lots of inputs. But it's > certainly a judgment call that may vary per app, per company, per user base, > and so on. > > > > But my point was to raise the observation for everyone who uses CFFORM (or > doesn't, because they didn't like the onsubmit validation which was > previously the only option.) > > > > /charlie > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Aaron Rouse > *Sent:* Tuesday, January 27, 2009 1:21 PM > *To:* [email protected] > *Subject:* [houcfug] Re: CFFORM Question > > > > Don't you think that would get old quickly for the user on a page with 200 > or so inputs? I know come about my 15th mistake I would be rather annoyed > by my 15th alert box. Although I still think that is just way too many > inputs for one page for any user who still maintains some level of sanity. > > On Tue, Jan 27, 2009 at 11:52 AM, charlie arehart < > [email protected]> wrote: > > Ramon (and others who might ever face such a challenge), while all the > suggestions so far are good ones, still one more that may suit your needs > would be to change CF's validation to happen when the user leaves the field, > rather than waiting until they submit the form. > > That's now an option, as of CF 7, though many missed the change. There's a > new ValidateAt attribute, and the values are onsubmit, onblur, and onserver. > <snip> … > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [email protected] For more options, visit http://groups.google.com/group/houcfug?hl=en -~----------~----~----~----~------~----~------~--~---
