The reason I tell people to stay away from CFFORM and CFINPUT is because when you make your form you know what you want it to do. Why make the server burn CPU cycles (not many, but unnecessary ones) to develop your JS validation code for you when you can just tell the system explicitly what to do.
If you like the validation code that CF returns, make a form with CFFORM and CFINPUTs, load it and view the source and lift the JS functions. Save them as a snippet and use them when you know you need to use them. Same thing goes for CFUPDATE and CFINSERT - why have the system figure out (excess processing) what SQL statement you want to run when you should be the one determining what SQL statement to run. t ********************************************************************** Tyler M. Fitch Certified Advanced ColdFusion 5 Developer http://isitedesign.com ********************************************************************** -----Original Message----- From: G L [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 13, 2002 8:53 AM To: CF-Talk Subject: CFFORM/CFINPUT Can someone explain to me why alot of advanced CF'ers don't like to use CFFORM and CFINPUTs in their code? I've even heard them refer to it as "novice cf-coding". I've always had good luck using them. Are there drawbacks to letting CF generate the js to validate your input fields? There must be a good reason. ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
