A single report has db connectivity issues

Question

Hello,
I have several reports connecting to our Informix db by logging on to the Informix online server.  All except one of these reports work fine.  We view all the reports using the .Net viewer in the browser.  This one report is able to open fine with the preview function of CR 2008, and when I navigate to the .aspx page that prompts for the parameter that page loads fine.
When I select the parameter and attempt to load the report I am immediatly greeted with one of four errors:
Database Connector Error: 'Error -1213: Character to numeric conversion error ' Error in File open_so_duedate {250A85C0-AF79-480D-B960-29598C0A3EAE}.rpt: Database Connector Error: 'Error -1213: Character to numeric conversion error '
Database Connector Error: 'Error -404: The cursor or statement is not available. ' Failed to retrieve data from the database. Error in File open_so_duedate {E15923B9-D213-4723-8013-C79BB196C7ED}.rpt: Database Connector Error: 'Error -404: The cursor or statement is not available. '
Database Connector Error: 'Error -400: Fetch attempted on unopen cursor. ' Failed to retrieve data from the database. Error in File open_so_duedate {250A85C0-AF79-480D-B960-29598C0A3EAE}.rpt: Database Connector Error: 'Error -400: Fetch attempted on unopen cursor. '
Database Connector Error: 'Error -349: Database not selected yet. ' Failed to retrieve data from the database. Error in File open_so_duedate {4161FB9D-1F8C-4EC8-9447-B015ADA29199}.rpt: Database Connector Error: 'Error -349: Database not selected yet. '
Yet if I leave the page there for a few minutes and then hit refresh the report occasionally opens.
I am not sure if this is the cause or effect or possibly irrevelant, but when this report fails to open we also get an error on the db side:
Sess  SQL            Current            Iso Lock       SQL  ISAM F.E.
Id    Stmt type      Database           Lvl Mode       ERR  ERR  Vers
137838 -              -                  -   Not Wait   -349 0    9.35
Last parsed SQL statement :
  SELECT * FROM bill_cust WHERE 0 = 1;
It should know the database, yet it is blank in that error.  This happens only on this report while others use the same datasource.  I have checked the .aspx page we use and it looks like it should.
Thanks

Answer 1

had to break into two posts for formatting issues
And when opened in CR 2011 and then saved in that format, the query becomes:
SELECT so_delivery.od_prom_date, so_delivery.od_ordr_item,
        so_delivery.od_wo, ship_cust.st_name, so_delivery.od_qty,
        so_delivery.od_qstat, so_header.oh_status, so_item.oi_qstat,
        part.it_part_rev, part.it_desc, part.it_base_part, part.it_status,
        part.it_um_stk, so_delivery.od_ent_date, wo.wo_class,
        wo_view.so_header_stat, wo.wo_status, vw_prod_grp.grp_item,
        wo_view.qty_in_stk, wo_view.qty_compl_first_op, wo_view.od_qty_due,
        so_item.oi_cust_pn, part.it_bmrt_stat, part.it_qc_stat,
        wo_view.sch_to_run_on, ship_cust.st_scust, vw_part.mfg_std_avg_pph,
        wo_view.wip_ship_hold, wo_view.inv_ship_hold, wo_view.sch_start_date,
        so_delivery.od_cur_prom_date, wo.wo_text1, wo.wo_text2, wo.wo_text3,
        wo.wo_text4, wo.wo_text5, wo.wo_text6, so_header.oh_ship_via,
        bill_cust.bt_stat, wo_view.sch_hrs_4_wo, part.it_need_validation,
        so_delivery.od_want_date, part.it_pish_or_pmd, part.it_pish,
        part.it_pish_date, part.it_pmd_rev_nbr, part.it_russ_stat, part.it_class,
        vw_prod_grp.grp_desc FROM   ssfnew@prod_on:informix.bill_cust bill_cust,
        ssfnew@prod_on:informix.ship_cust ship_cust,
        ssfnew@prod_on:informix.so_header so_header,
        ssfnew@prod_on:informix.so_item so_item,
        ssfnew@prod_on:informix.so_delivery so_delivery,
        ssfnew@prod_on:informix.part part,  OUTER ssfnew@prod_on:informix.wo wo,
        ssfnew@prod_on:public.wo_view wo_view, ssfnew@prod_on:public.vw_prod_grp
        vw_prod_grp, ssfnew@prod_on:public.vw_part vw_part WHERE
        (bill_cust.bt_bcust=ship_cust.st_bcust) AND
        (ship_cust.st_scust=so_header.oh_scust) AND
        (so_header.oh_ordr_nbr=so_item.oi_ordr) AND
        (so_item.oi_ordr_item=so_delivery.od_ordr_item) AND
        ((so_item.oi_part_nbr=part.it_part_nbr) AND
        (so_item.oi_part_rev=part.it_rev)) AND (so_delivery.od_wo=wo.wo_nbr) AND
        (wo.wo_nbr=wo_view.wo_nbr) AND (part.it_part_rev=vw_prod_grp.part_rev) AND
        (vw_prod_grp.part_rev=vw_part.part_rev) AND so_header.oh_status>-1 AND
        so_delivery.od_qstat='O' AND so_item.oi_qstat='O' AND
        vw_prod_grp.grp_item='ca_ext' AND so_delivery.od_prom_date<=DATETIME
    (2011-10-24 00:00:00.) YEAR TO SECOND ORDER BY vw_prod_grp.grp_item
The issue is in the OUTER.  For some reason CR 2008 does not put parens around ssfnew:informix.wo wo,
    ssfnew@prod_on:public.wo_view wo_view.  If we run the 2008 query with the parens in place the query finishes in 23 seconds as opposed to not finishing.  Why the report sometimes loads is still a mystery.
We are tearing apart the report to see if rebuilding it will generate the correct SQL query, but this is not reasonable if we have several reports with this issue.