Databases
StackOverflow2013
Postsdbo
POCrystal Reports: How can I avoid nested subreports in this case?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCrystal Reports: How can I avoid nested subreports in this case?
    primarykey
    data
    text
    <p>I have a main report which contains user information -- and a subreport that contains multiple items for said user.</p> <p>Question is, I need the main report to duplicate as many times as necessary for the number of users I feed into the DataSource -- how can I do this, so that it results in one large report (containing multiples of the main report)?</p> <p><strong>EDIT:</strong> Let me re-ask with a specific example (similar to my own): Let's say I want a report for a grocery shopper -- all of the shopper's demographics would be on the main report, however, there needs to be a section (or subreport) for a specific shopping trip containing all items purchased.</p> <p><strong>NOW</strong>, here is the clencher. I need to run this report for many different shopping trips (this also means different shoppers too).</p> <p>It might even be better to say that this is a "shopping trip" report, which can run for a batch of shopping trips.</p> <p><strong>FURTHER PROGRESS:</strong> How can I get the grouping to work when my data looks like this:</p> <pre><code>(shoppingTripId, shopperId, shopperName, shoppingDate, itemBought) ------------------------------------------------------------------ 1, 1, Chris, July-24-2009, Computer 1, 1, Chris, July-25-2009, Laptop 2, 3, John, June-14-2009, Ipod 2, 3, John, June-14-2009, Television </code></pre> <p>The report, if all goes well, would look like this:</p> <pre><code>+----------------------------------------------- | Chris ShoppingTripID: 1 | 123 Main Street CustomerID: 1 | Anytown, CA 90210 +----------------------------------------------- | Computer $999.00 | Laptop $1099.00 +----------------------------------------------- +----------------------------------------------- | John ShoppingTripID: 2 | 123 Main Street CustomerID: 3 | Anytown, CA 90210 +----------------------------------------------- | Ipod $999.00 | Television $1099.00 +----------------------------------------------- </code></pre> <p>At the moment, I'm getting this:</p> <pre><code>+----------------------------------------------- | Chris ShoppingTripID: 1 | 123 Main Street CustomerID: 1 | Anytown, CA 90210 +----------------------------------------------- | Chris ShoppingTripID: 1 | 123 Main Street CustomerID: 1 | Anytown, CA 90210 +----------------------------------------------- | John ShoppingTripID: 2 | 123 Main Street CustomerID: 3 | Anytown, CA 90210 +----------------------------------------------- | John ShoppingTripID: 2 | 123 Main Street CustomerID: 3 | Anytown, CA 90210 +----------------------------------------------- | Computer $999.00 | Laptop $1099.00 +----------------------------------------------- | Computer $999.00 | Laptop $1099.00 +----------------------------------------------- | Ipod $999.00 | Television $1099.00 +----------------------------------------------- | Ipod $999.00 | Television $1099.00 +----------------------------------------------- </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USC. Griffin
    1. USC. Griffin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCrystal Reports: How can I avoid nested subreports in this case?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCrystal Reports: How can I avoid nested subreports in this case?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload