Hi,

I receive error "Error in reading sort file record: 1 field scanned, 253 expected" while printing a invoice.

Can anyone tell me how can i keep a trace and get the exact table/field causing an error. I can't keep report in debug mode in live environment.

Please help me its very eargent.

Hi,

I receive error "Error in reading sort file record: 1 field scanned, 253 expected" while printing a invoice.

Can anyone tell me how can i keep a trace and get the exact table/field causing an error. I can't keep report in debug mode in live environment.

Please help me its very eargent.

Hello,

This error comes when one of the input variables to the report have a corrupt value.

Hope this helps

Regards

But can i get exact field and table which is correpted without keeping any component in debug mode....

But can i get exact field and table which is correpted without keeping any component in debug mode....

Hello,

maybe you will be able to get the information from your logfiles.

Regards

Hi,
This is usually caused by Excel !!
More to explain, while entering data in baan, if data is copied from an excel spreadsheet cell to a baan field like description field, it also copies the end of cell charecter from cell and paste into baan field as a new line charecter ! Now, if this field is available for editing, when you browse through the fields of this session (using tab), and reach this perticular field (lets say description), value in the field disapears. And when you press tab and move away from this field, value in the field apears again. When this field is used in a report, the new line charecter adds a new line in the detail layout and causes more lines in the report than expected. Thats why you get this error. Having known this, please check if this is the problem you are facing and try to find the fields and correct them. It can be any field printed on the report and record will be within the selection criteria of the report.

With Due respect to one of My Senior who identified this problem,
Best Luck, Shree

If you tell your users to use the -nodebug option than you can debug. That's the only one to find out (at least I do it that way). However if you are fast enough you can perhaps intercept the tmp file in $BSE_TMP.

Regards,
Han