Problem of a combined graph

Question

Hi, guys:
I am trying to build a combined graph with bars and line. I built two series of query.
series 1 for bar chart:
select null link, to_char(inv.invdate) label, sum(inv.amt) total$
from invoices inv, payments pa, clients cl,
(select to_date(:P390_DP_START_DATE,'MM/DD/YYYY') + rownum -1 date_in_range
from all_objects
where rownum <= to_date(:P390_DP_END_DATE,'MM/DD/YYYY')-to_date(:P390_DP_START_DATE,'MM/DD/YYYY')+1) days_in_period
where inv.invoicekey=pa.invoicekey
and cl.clientkey=inv.clientkey
and inv.invdate=days_in_period.date_in_range
and inv.debtorkey not in (11352, 11353)
and exists (select tr3.transkey
from transactions tr3
where tr3.transkey=pa.transkey
and tr3.type=1)
group by inv.invdate
order by inv.invdateseries2 with line chart
SELECT null link, to_char(days_in_period.date_in_range) label, count(cl2.clientkey) "Total Factored Clients"
FROM Clients cl2, 
(select to_date(:P390_DP_START_DATE,'MM/DD/YYYY') + rownum -1 date_in_range
from all_objects
where rownum <= to_date(:P390_DP_END_DATE,'MM/DD/YYYY')-to_date(:P390_DP_START_DATE,'MM/DD/YYYY')+1) days_in_period
where exists
(select tr.transkey
from transactions tr
where tr.clientkey=cl2.clientkey
and tr.type=1
and trunc(days_in_period.date_in_range)-1-trunc(tr.postdate) <= 90
group by days_in_period.date_in_range
order by days_in_period.date_in_rangeHowever, the first query returns less rows than the second query, as there are some days such as weekend without total$, but with Factored Clients. In the combined graph, it shows first only rows with data for both query, and then show dates with only Factored Clients. How can I solve this problem in APEX or I have to make sure there are same number of rows in both series?
Thanks.
Sam

Answer 1

"but am unable to do so" doesn't explain anything. What, exactly, is your problem? You can't make it compile? The graph comes out upside down?
Before you reply, please click the link "special tokens" above the Subject of a reply. That will show you how to post code.
Next thing is to comment closing curly braces that are more than a short distance from their opener:
  } // end of foo()
} // end of class BarNext thing is to use methods. For example, that huge set of if tests to set "scale" should be moved into a method that sets scale:
  public void paint( Graphics g ) {
    scale = setScale( maxValue );
  } // end of paint()
  private int setScale( int max ) {
    if ( . . . // etc.
} // end of class BarGraphAppAnother thing would be to add "else" keywords so that those "if"s wouldn't all be tested:
  if ( max > this && max < that ) scale = x;
  if ( max > this2 && max < that2 ) scale = y;
  // should be:
  if ( max > this && max < that ) scale = x;
  else if ( max > this2 && max < that2 ) scale = y;In the second way, the second test isn't evaluated if the first one is true and "scale" is set to "x".
And while I'm looking at that particular piece of the code, how about replacing most of it with:
  private int setScale( int max ) {
    if ( max < veryLargeWhichIsSpecialCase )
      return (max + 599)/600;
    // special case goes here
  } // end of setScale()Implement some of this, and then repost the relevant section of code with a specific question, like "why does the graph come out backwards?"