> <query to get value>
>
> <loop query> <!---figure individual component status in each
> of three areas--->
>
> <cf_childtaga attribute1="#query.value1#"> <cfquery updates
> table with values from childtag a>
>
> <cf_childtagb attribute1="#query.value1#"> <cfquery updates
> table with values from childtag b>
>
> <cf_childtagc attribute1="#query.value1#"> <cfquery updates
> table with values from childtag c>
>
> <end loop>
>
> <another loop> <!---figure components overall status based on
> status of three areas calculated above---> <query processes
> new inserted values and creates another new value>
>
> <query updates another table with the new value> <end loop>
>
> <another loop> <!---figure sets overall status based on the
> status of the compoents it contains---> <query processes new
> inserted value and processes another new value>
>
> <query updates another table with the new value> <end loop>
> <!---end parent tag--->
>
> The attributes the child tags are expecting is a setid and a
> component type each. I didn't use cfinclude becuase I didn't
> think I could pass attributes to it.
I'm sorry, but I'm finding your pseudocode quite confusing. You might want
to post the actual code.
> What's cfmodule?
It's a tag that allows you to call custom tags with a TEMPLATE attribute,
instead of using "CF_". For example, assuming that foo.cfm was in the same
directory as your page, <cf_foo> would be equivalent to <cfmodule
template="foo.cfm">. The advantage of CFMODULE is simply that it allows you
to specify exactly which "foo.cfm" you want to use, and doesn't rely on the
custom tag directories.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
