> If I'm reading you right, I may just need ONE application.cfm in the root > of my directory structure?
Yeah, it sounds like a semantic problem more than anything! ;-) As CF has a pretty specific definition of an "application", so think of your app as "the collection of web pages that someone accesses through the single login". Then just think of your subdirectories as "sections", "tools", "areas", or whatever, within your app. Here's some basics: - Put Application.cfm in the the root - It doesn't need to have a capital "A" in the filename on Windows, but you may as well - it saves a lot of hair-pulling the first time you port a CF app to Unix ;-) - Define the app in Application.cfm with the CFAPPLICATION tag: <cfapplication name="appName" sessionmanagement="Yes" setclientcookies="Yes"> - Once you've authorised the user's login details, set their session variables. - Call a tag from inside Application.cfm that checks for the existence of a specific session variable that you set for each login - if it doesn't exist, use CFLOCATION to redirect them to the login page. Users will be able to access all pages in the root and in all sub-directories using the same login. Let me know if I've got your intentions wrong here... - Gyrus ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - [EMAIL PROTECTED] work: http://www.tengai.co.uk play: http://www.norlonto.net - PGP key available ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
