ReportPro 2.40 for X#: empty report while showing correct in VO ReportPro 2.31

[ic2]

There seem to be more issues with the X# ReportPro. I have a working report with an indexorder, no filter, a seek value defined as

Code: Select all

"62020007049000"

and a while value, defined as

Code: Select all

left(Laadlos3.A6ritnr,13)=="2020007049000"

These are valid values which I can find in the DBF. The VO ReportPro 2.31 Preview directly shows a report with content of this specific record.

But when I open the same report in the X# ReportPro it quickly shows "Calculating page count" and then you see an empty report with a magnifying glass with a cross in it. As if nothing could be found. When I remove the While condition and only seek "6" (or 6, without quots), many 1000 records start with 6 in this index tag, I immediately see the empty report.

Is there something different in the X# ReportPro index/seek/while I am unaware of? WHat else could cause a perfectly valid VO report to remain empty in the X# ReportPro (2.39 or 2.40)?

Dick

[robert]

Dick,
This could be something in RP2 or in the RDD system.
An example report + dbfs could help to find this.

Robert

[ic2]

Hello Robert,

I may have some clue. The main dbf (the one on top of the section) contains millions of records. I wanted to empty it before sending it to you except for a handful of records and after I did, the report showed correctly in the X# ReportPro preview too, like it already did in the VO ReportPro with the full DBF.

Does this already give you some clue? Otherwise I will gladly send you the rpt + DBF's but I need to send you multiple GB's of data.

PS: I just posted a (quick) reply which wasn't visible after wards. Retyping and 2nd attempt....

Dick

[robert]

Dick,
Please use Wetransfer or something like that and send us the link to the actual data that shows the problem.

Robert

[robert]

Dick,
I have analyzed the DBF file and found the problem:
The RDD has a problem in the calculation of the # of records in the file (during the opening of the DBF), which causes an exception during the opening of the file.
I'll send you an updated DLL by mail.
This error by the way, only occurs with VERY large files, In your case the file is 2,71 Gb and has 4.693.175 records. That is quite unusual.

Robert

[ecos]

Robert,

you're right, small files like this are very unusual
(sorry, couldn't resist)

Karl

[Chris]

[ecos]

some more...

[robert]

I was wondering if I should change the RDD system to allow for bigger files.
These numbers have convinced me that I should do that.

Robert

[ic2]

Thank you very much for finding the cause. I am glad my conclusion that it was related to the size was correct. Yes I think indeed that large dbf's should work. After all, it did work in VO without that problem with the same large dbf.

I'll await your updated DLL!

Dick