Perhaps would be helpful to point out that in my similar application, at least, in application.cfm page, I also key the application to the ID, as in: <CFAPPLICATION Name="MyBusiness#Request.BusinessID#" sessionmanagement="yes" sessiontimeout="30"> (So, each "site" is a separate application even though using only one set of code/templates.) Then see if an application structure already exists (created from a series of queries to set a structure that includes all the unique info for that specific entity). (Use appropriate locking procedures.) If the application.structure exists, then duplicate it to request scope. If application.structure does not exist (or isn't for some reason a structure), go and run the procedure that sets up the structure, making it an application structure, then duplicate it to request scope. So, each page call is duplicating the basic informational structure into request scope (setting it up first if not available). This make the informational structure appropriate to the identified business available to any page called, and can be referenced as in: #request.stBusinessInfo.City#, #request.stBusinessInfo.State# (no need for locking as not in session or application scopes). You can also use cfdump (cf5 or later--or use the custom tag if before) to *see* this structure request.stBusinessInfo.
Hope this gives a little more to help you develop your application. Keith Dodd [EMAIL PROTECTED] www.wingserv.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
