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 any errors either.
Now you're of course going to run into issues with <cfform format="flash">, but it didn't sound like you were using that. Jake Pilgrim ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:272170 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4