I think it is more a case of how little people use CFFORM anymore, it could be that it's use in the past was an easy option for forms and a kind of beginners tool.
I know we never use CFFORM anymore for this reason and we never looked at x-forms cause we generated most our forms on the fly. As for Flash forms, urgh...nothing good to say. :-) "This e-mail is from Reed Exhibitions (Gateway House, 28 The Quadrant, Richmond, Surrey, TW9 1DN, United Kingdom), a division of Reed Business, Registered in England, Number 678540. It contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender or call our switchboard on +44 (0) 20 89107910. The opinions expressed within this communication are not necessarily those expressed by Reed Exhibitions." Visit our website at http://www.reedexpo.com -----Original Message----- From: Mike Kear To: CF-Talk Sent: Mon Nov 13 05:38:42 2006 Subject: Re: CFForms/XML format suddenly giving error messages Thanks to Roland Collins on an other list, who pointed me at the solution. What surprises me most about this is that so few people have tried the XML forms. They run FAR faster than the flash versions and are MUCH more flexible as to look and feel. However flash is the buzz-word of the moment and so few people know anything about CSS. Anyway .... So I'm suddenly getting this problem ... I think its to do with the location of the default scripts, css and xsl files. I have a solution - kind-of. I created a folder called CFFORMS under the root of my site and moved a clean new copy of the /cfide/scripts/CSS folder and /cfide/scripts/XSL folder in there. Then I changed the CFFORM tag to access the skin file directly, rather than by name. e.g. Instead of : <cfform name="forminput" method="post" action="#cgi.SCRIPT_NAME#" format="xml" skin="silver" preservedata="yes" scriptsrc="/CFIDE/scripts"> I now use <cfform name="forminput" method="post" action="#cgi.SCRIPT_NAME#" format="xml" skin="/cfforms/scripts/xsl/silver.xsl" preservedata="yes" scriptsrc="/cfforms/scripts"> And that seems to have done the trick. I was trying to change the scriptsrc attribute to fix the problem, but instead it was the location of the skin xsl file that was the problem. Thanks for your help, Roland. I'm sorry if this problem has been cross-posted, but I was having problems finding anyone who knows anything about XML forms. If you haven't played with the XML forms, I strongly suggest you give them a try - all the validation stuff works as advertised (unlike the clunky version in CF5). Rather than waiting for a full minute for a flash form to render, it renders instantly like html, you can build them automatically from a table definition too as I do every day. They are the great unsung hero of CF7. Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks Pty Ltd http://afpwebworks.com Full Scale ColdFusion hosting from A$15/month ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:260144 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
