Re: input vs cfinput

Thanks for the help. ~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion Archive: http://www.houseoffusion.com/groups/CF-Tal

RE: input vs cfinput

> I found a few older forms that use cfform, but then use just > html tags. > > Not sure why they are that way, (of course it is not > commented) but i don't want to have to rebuild them at this point. > > just wondering if there are any issues that can come from > this type of usage. No, i

Re: input vs cfinput

I've encountered that before too. Yes, you scratch your head, maybe even shout out a "why the hell did they do that?", but in the end - no, plain HTML inputs don't seem to conflict with CFFORM inputs. You of course can't leverage the extended attributes of a cfinput, but it's not going to throw

input vs cfinput

I found a few older forms that use cfform, but then use just html tags. Not sure why they are that way, (of course it is not commented) but i don't want to have to rebuild them at this point. just wondering if there are any issues that can come from this type of usage. ~~~