Bryan S wrote:
Whenever two reports are running at the same time the reports produce random results.
Can you define "random"?
I believe this behavior is caused by the values of the variables scope variables in my cfcs being changed by one report process and then being used by the other report process.
Certainly possible--the variables scope is available to the entire CFC, so if you have two functions accessing a variable in the variables scope, or two threads hitting the same CFC in the shared scope, then they're both using the same variables-scoped variable. So if one request changes that variables-scoped variable, and the CFC is in the application scope for example, then all requests using that CFC are affected by that change.
I know that once compiled the cfc remains static until a HardRefresh. I am not clear about how instances of the cfcs are created and how they would interact in these circumstances.
Depends on how you create them and where you put them--would need more info here. If you're putting your CFC in the application scope, then yes, it would remain unchanged unless you replace that application scope variable with something else, or you restart the application.
When two reports are running at once what ends up in these directories is different from when only one is running at once.The path to this directory is stored in the variables scope of my service.
Probably need to see some code to see exactly what you're doing, but if the *directory* is common between the two reports, then that's fine. If the *file names* between the two are *not* common and you're putting that in the variables scope, chances are that's where you're going wrong.
Variables that are unique to a request and/or you don't want leaking out of the confines of a function need to be put in the var scope.
-- Matt Woodward [EMAIL PROTECTED] http://www.mattwoodward.com/blog Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html
smime.p7s
Description: S/MIME Cryptographic Signature
