becks22
22nd June 2009, 15:15
Hi ,
While running a report in a particular company I am encountering an error
as
"Error in reading sort file record: 70 fields scanned ,120 expected
but same report runs well in other comapnies ..Please help
mark_h
22nd June 2009, 16:43
Sounds like the input file is corrupt for the report. My suspicion is in the data - run it in debug mode and check the file looking for control characters in the data. I have seen this before. I am also assuming you have recompiled and made sure the current objects are in this company.
bdittmar
22nd June 2009, 21:19
Hi ,
While running a report in a particular company I am encountering an error
as
"Error in reading sort file record: 70 fields scanned ,120 expected
but same report runs well in other comapnies ..Please help
Hello,
This error often comes when one of the input variables to the report have a corrupt value.
Regards
becks22
24th June 2009, 10:27
can i knw which report variable is having corrupt value ??
bdittmar
24th June 2009, 10:44
can i knw which report variable is having corrupt value ??
Hello,
Check the values for your sorted report input fields, there may be corrupt data in one of them.
Regards
Rajhyd
24th June 2009, 11:39
Hi,
Can you run the report for smaller ranges. This would help you in narrowing down the date or other criteria based on which the report runs. Once you get to know this, check the data in the relevant fields/tables. This error occurs when there is # or any character in a field or also an empty space. Sometimes user accidentally press the space bar in a field and the value gets stored.
Hope this helps.
Regards
Rajasekhar
amitmmokashi
24th June 2009, 13:40
Hi,
You can actually debug the report and check the sorting of fields in the function 'r.read.seq.file()'. The 71st field in the function is having some erroneous value. The variable 'scan.ret' is throeing the error message.
Regards,
Amit
loveneesh
26th June 2009, 09:35
There may be currupt data in your table for index field maintained in report input field.
Try to run report with presorted index option instead ascending in report input field.
rrocks23
2nd August 2009, 08:09
sometimes u get this msg when u divide something by zero :)
Joy Conner
14th November 2010, 21:06
I have read the posts on this subject and it is not clear to me what to do given what I am seeing.
The problem seems to occur at function extern r.write.seq.file() The variable that is a problem have a value of ++ and just prior to this it had a value of 0. The variable is a double, so I am not sure how it's value became ++
Any help will be greatly appreciated.
- Joy
BaanInOhio
15th November 2010, 01:11
A "++" value in a double/long field is caused by a divide by zero from a report 'print expression' field. If a report print expression field contains a calculation that could result in a divide by zero condition, I use a "question mark" statement to force the result to zero when the denominator is zero.
print expression: (bottom = 0) ? 0 : top/bottom
The result of divide by zero "++" will terminate the string.scan that is done to return the fields from the report's sort file, causing the "error reading sort file" condition.
Joy Conner
15th November 2010, 16:05
I found the problem. Thank you.