This is another one of those huge application issues - though could apply else where I guess.
If you have your <cfapplication in your app_globals file and don't have some sort of code to ensure it only runs once, you could get odd database happenings in MX. We have multi applications that call each other, and they switch app_globals when module calling each other. This is a necessary evil of the master application. We were experiencing data loss when the client variables were being written to the database. It appears that the <cfapplication can only run *once* per request (which it would do in the application.cfm file). We are guessing it does some init stuff that gets kludged when called more than once (it was being called several times). There is also, obviously, a performance increase by running it one time. This never caused an error in 5 - it is, however sloppy. Most probably don't cross applications in one request, and this more than likely wont apply to many. Cheers, Rob ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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
