|o| your development in due course. You might not want to put your |o| header and |o| footer on application.cfm and onrequestend.cfm respectively. Though it |o| works, its not meant to put templates or any visual display |o| items. It's not |o| a standard practice either. |o|
Guess I didn't make it clear, or atleast don't understand. the files header.cfm and footer.cfm are actually called by CFINCLUDE in the Application.cfm and OnRequestEnd.cfm. The graphic elements are not actually in the Application file. Is still not a good idea? I'd gotten the idea to that from a guide I was reading. Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
