> My understanding of your words was that storing the datasource in an > application variable is good because you can copy it into the local scope > and avoid locking. That is a resolution of the problem, but does not > address the issue of using an application variable to store the > datasource. :) > It is kind of like saying "I lost my keys, have you seen them?" and > answer "Break a window to get into the house."
To me, that's a perfect example of why e-mail will always play second fiddle to a voice conversation. Based on what you say, it was just a misunderstanding then, as I never meant to suggest that it was *good* to store it in an application variable because you can copy it to a local scope. Not at all. Without belaboring this thread, pre-MX, I don't advocate using shared-scope varaibles such as the application scope for these sorts of variables. Period. Regards, Dave. Regards, Dave. ______________________________________________________________________ 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
