Hi Tom,
If you want multiple circuits to share a particular fuse, why not put the shared fuse
in a "shared" directory under the
home directory? No need to use cfmodule, just a simple cfinclude call from any
circuit:
<cfinclude template="#fusebox.rootpath#shared/qry_usedalot.cfm">
It works with the fusebox.org core, there's no duplication, no issues with scoping,
and it's a common and
well-understood practice. It's just like any other fuse.
What do you think?
LeeBB
----- Original Message -----
From: Tom Schreck <[EMAIL PROTECTED]>
I've tried using cfmodule to call a query from a centralized location,
but my query was picking up Attribute values that are present at the
time of the call to the cfmodule, but were not passed into the cfmodule.
Here's a snippet on how I structure my queries:
<cfparam name="Attribute.numVariableID" default="0">
<cfquery>
SELECT * from TableName
WHERE 0=0
<cfif Attribute.numVariableID GT 0>
AND TableName.numVariableID = #
Attribute.numVariableID #
</cfif>
</cfquery>
So, I'm CFMODULE-ing a call for this query and not passing numVariableID
to the query call. The variable is present at the time of the cfmodule
call, but not being passed. Somehow the cfmodule recognizes the
variable and includes it in the query execution. The query is stored in
a different circuit all together. To get around this, I have to place
the query in each circuit. The kicker is I can still use cfmodule to
call the query, but since it's in the same circuit there's no problem.
I run into problems when I cfmodule to a different circuit. Any
help/suggestions on this would be appreciated.
Does anyone have any FuseQ examples? I'm looking at how to best manage
have my query files in 1 location versus copying them into each circuit.
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================