Best Practices - Multiple Tables

[Former Member]

Post Author: lpangelrob

CA Forum: Data Connectivity and SQL

Hmm. I like this forum much better.Anyways... we're a futures company, and SQL Server 2k5 is set up so that there are a couple of ways to get the previous trade date and put it into the report. I want the previous trade date in the report, but I generally can never link the data in the report to the date table, so I get the warning "Your current link configuration contains multiple starting points. / Please be advised that this is generally not supported."6 reports in, it seems as though this creates some problems. When I try to plug in the date from this second starting point, it continuously comes up as blank.Are there any other good ways to plug in arbitrary distinct data (e.g. "select max(process_date) from date_table where process_flag = 'Y'") besides adding commands through Database Expert?

[Former Member]

Post Author: PeterLiebich

CA Forum: Data Connectivity and SQL

Subreports are definitenly the ant's pants. I had a KPI report for a company with 25 different branches, they wanted them ranked by nearly 20 different KPI's with the last one being a ranking of the KPIs. Did it all with subreports and shared variables

[Former Member]

Post Author: sestes

CA Forum: Data Connectivity and SQL

I use them frequently and in one unusual case I used more than a dozen subreports on a single report. However; like many report components, they can affect performance depending on how it's used, data structures etc.

[Former Member]

Post Author: lpangelrob

CA Forum: Data Connectivity and SQL

That sounds like a plan... I was wondering if subreports were in the "things to use sparingly" pile in the toolbox. Between extra commands and subreports, it sounds like subreports are the way to go.

[Former Member]

Post Author: PeterLiebich

CA Forum: Data Connectivity and SQL

Create a subreport with the second table - no need to link it to the main table

If you only want to get a signle piece of information (eg max(process date)) then stick the sub-report in a section of the report header and suppress the printing. In the sub-report you should set a Shared variable.

In the main report create a formula which references the shared variable. Note. You will need to set the evaluation time of this formula to "WhilePrinitingRecords" to ensure that it evaluates after the sub report