No, then you would just re-create your chasm trap.
See also:
Tips & tricks section from Business Objects
SQL Challenges by Integra Solutions (start with page 16)
Sometimes you can force your results from a synchronized query into one block after the initial run. You just have to be careful how to interpret the data:
For example (the following is a fan trap scenario, from memory so there might be some flaws):
Order header table
Order Nbr Customer Amount
--------------------------------
005 Bobette 100
007 Bob 50
Order detail/line table
Order Nbr Order Line Product Nbr of Items
-----------------------------------------------------------------------
005 1 Book: My Idaho 1
005 2 Plasma screen 10
007 1 Book: History of the Corvette 1
Data provider
Result objects: Order Nbr (dimension), Amount (measure), Order Line (dimension), Product (dimension)
Result (with contexts to avoid a fan trap):
Order Nbr 005 (Master/Detail section)
Table 1 Table 2
Amount Order Line Product
Order Nbr 007 (Master/Detail section)
Table 1 Table 2
Amount Order Line Product
You receive two tables, because you are asking for information (Order Line and Product) for which the Amount cannot be spread across (Order Amount is not stored at the Order Detail table level).
You can force all the info into one block/table (manually re-formatted after initial run):
Table
Order Nbr Amount Oder Line Product
---------------------------------------------------------------
005 100 1 Book: My Idaho
005 100 2 Plasma screen
007 50 1 Book: History of the Corvette
Total: 150
If you would not use contexts at all the following would happen:
Table
Order Nbr Amount Oder Line Product
--------------------------------------------------------------
005 100 1 Book: My Idaho
005 100 2 Plasma screen
007 50 1 Book: History of the Corvette
Total: 250
Notice the total of 250 for Amount is incorrect (as a result of the unresolved fan trap).
Andreas (BOB member since 2002-06-20)