My feeble understanding of Fuse methodology suggests that the query
fuse should return a completed rowset, ready for use by the display
fuse.
Thus, do all secondary lookups in the query fuse.
Put a different way. The Display fuse should not have to worry at all
about the query, it's sole purpose in life is to display the rowset
as directed, so the rowset should come to it whole and complete.
hth
On Dec 6, 2005, at 5:01 PM, Christian Cypert wrote:
I'm getting myself confused on what I think is something straight
forward.
Using Fusebox I have a query that returns a selection of records
that I place into a Rowset in my query fuse. Now the question is
how do I do the following while staying within the Fusebox framework.
With each row in the Rowset I need to do a secondary query on
another table and return a set of records to display with the main
query. I'm not sure how to put this into a fusebox framework.
I basically need to do the following.
Query([TableA];[TableA]Something=SomethingElse)
For ($i;1;records in selection([TableA])
Display information from TableA
Query([TableB];[TableB]Anything=AnythingElse)
Display information from TableB
end for
If I use a query fuse and then go to a display fuse how can I fit
the secondary query within the for loop when displaying records in
the display fuse?
Hope that makes sense.
--
Bart Alcorn AvantraNet, Inc.
Office: 678-580-3265
Mobile: 770-335-5518
AIM/iChat: AvantraNet
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
