No you don't need to put the doctype in the Application.cfm (use a capital A by the way). Having a whole stack of CF logic before the doctype *may* through it into quirks mode because depending on your output settings. This is because by default CF does output white space characters in normal code, even if there is no other output. If this white space reaches IE's limit you'll suddenly find yourself in quirks mode.
For example: <cfif something EQ somethingelse> <cfset x = y> </cfif> will generate some white space but nothing else. This is not a problem on its own but if you have enough cf code you might end up with enough whitespace to trigger it. If you are worried about this there are ways to stop CF outputting anything - check <cfsilent> and <cfsetting enablecfoutputonly="Yes">. Cheers Mark -- Mark Stanton Technical Director Gruden Pty Ltd Tel: +61 2 9299 9462 Fax: +61 2 9299 9463 Mob: +61 410 458 201 http://www.gruden.com mailto:[EMAIL PROTECTED] --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
