I run SQL Profiler and looked for the query where the problem is, and IMHO, it's a bug in the assumption of the "14" transaction, which is an adjustment transaction. There is also a posted flag. But IMHO, after the aged table is updated, the process should go through it and remove blank records.

Here is the query from the profiler.

Select "IDCUST","IDINVC","CNTPAYMNBR","IDRMIT","DATEBUS","TRANSTYPE","CNTSEQNCE","AUDTDATE","AUDTTIME","AUDTUSER","AUDTORG","DEPSTNBR","CNTBTCH","DATEBTCH","AMTPAYMHC","AMTPAYMTC","CODECURN","IDRATETYPE","RATEEXCHHC","SWOVRDRATE","IDBANK","TRXTYPE","IDMEMOXREF","SWINVCDEL","DATELSTSTM","IDPREPAID","IDCUSTRMIT","DATERMIT","CNTITEM","FISCYR","FISCPER","RATEDATE","RATEOP","STMTSEQ","PYMCUID","DEPSEQ","DEPLINE","CODETAX" from "AROBP" where (("IDCUST" = 'SBSA1301    ')) AND (("DATEBUS" >= 0 AND "CNTPAYMNBR" = 0 AND "IDINVC" = '                      ' AND "IDCUST" = '            ') OR ("CNTPAYMNBR" > 0 AND "IDINVC" = '                      ' AND "IDCUST" = '            ') OR ("IDINVC" > '                      ' AND "IDCUST" = '            ') OR ("IDCUST" > '            ')) AND (("IDCUST" = 'SBSA1301    ') AND (("DATEBUS" >= 0) AND (("DATEBUS" <= 20220908) AND ("TRANSTYPE" = 14)))) order by "IDCUST","IDINVC","CNTPAYMNBR","DATEBUS","IDRMIT","TRANSTYPE","CNTSEQNCE" option(fast 10);

Edit the Crystal report to suppress blank lines, it's a very old bug on that report.

Thanks Jay. We don't have the latest version of Crystal Reports. Any chance you can email the updated report to me? lipdav at gmail.com