Here is a broad, general question that is related to the philosophy of Kool report. I surely hope you will give me a more than one word answer. I have some data in a table. Some of the related data is in a second table. I do this type of thing in Excel frequently. If I want to build a datastore (so I can create a chart). Am I better to do this fairly complex manipulation in SQL and just create new table which directly addresses what I need, or is piping and the koolreport functions (sort, limit, join, etc) good enough to handle it? I'd prefer a pragmatic answer rather than a theoretical one.