Hey Scott,
Ya I prefer server side as well....
Thanks for the points about logging common data entry errors and WML considerations.
Good call :o)
Scott Knaub wrote:
> Server side validation is my choice.
>
> For me, it eliminates wondering if the browser version supports client side
> validation through JavaScript. If I'm concerned that the client doesn't
> support it, I have to write the server side validation for that possibility.
>
> I also have more control over how I validate the fields and how forgiving I
> am to the user for common mistakes or various ways to enter data. A Social
> Security Number, for instance, could be entered with or without the dashes
> between the numbers. Maybe a user would put spaces between the numbers. I
> built a custom tag called CF_CheckSSN (it's on Allaire's Developers
> Exchange) which allows a user to enter a SSN any which way and, as long as
> there are 9 numbers somewhere in the input field, the custom tag formats it
> with and without dashes and passes the information through.
>
> As for the issue about hits, that's what the Web server is built to do so I
> say let them hit it.
>
> Other advantages of server side validation:
>
> With Server side validation, I can build a log of common mistakes entered
> into a form and then redesign the form to help the user enter the
> information properly the first time.
>
> Then there's the thought about Wireless Markup Language (WML). If we start
> coding with server side validation, our code is much more reusable when our
> client changes.
>
> -----Original Message-----
> From: Bryan [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 17, 2000 11:46 AM
> To: [EMAIL PROTECTED]
> Subject: To CFFORM or not to CFFORM
>
> Hey All,
>
> I've debated this issue with my local associates many times, so I
> thought I'd throw it out there and see what some other folks have to say
> about it.
>
> Do you use CFFORM and it's built in client side form element validation,
> or do you use a server side approach (i.e. do some error
> checking...build an error message and display it)?
>
> My pet peeve with CFFORM is the javascript pop-up windows show one at a
> time which could drive a user crazy. If you use a combo of both client
> and server side validation, you could confuse the user (which we all
> know get confused very quick). They think they've filled in the form
> properly and then all of a sudden they are looking at a list of new
> errors.
>
> Of course CF 4.5.1 has the "onvalidate" attribute in cfinput which
> allows you to expand the kind of validation you can do, but you're still
> stuck with one error message at a time.
>
> There is also the issue of hits on the server. Of course client side is
> better here.
>
> Comment away...suggestions welcome...custom solutions??
>
> Thanks in advance
>
> Bryan Stevenson
> Electric Canvas Technologies
> Inter/Intranet Development
> www.ecanvas.com
> [EMAIL PROTECTED]
> (250) 920-8830
> -------------------------------------------
> Allaire Alliance Partner
> www.allaire.com
>
> ----------------------------------------------------------------------------
> --
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
> ------------------------------------------------------------------------------
> To Unsubscribe visit
>http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
>message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
--
Bryan Stevenson
Electric Canvas Technologies
Inter/Intranet Development
www.ecanvas.com
[EMAIL PROTECTED]
(250) 920-8830
-------------------------------------------
Allaire Alliance Partner
www.allaire.com
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
