Allow skipping EOF validation in row block processing
See original GitHub issueBecause of this piece of code:
We are having trouble reading XLS files generated by a 3rd party. This has been discussed for example here. So Excel itself and validators allow such invalid format and fix it during saving, but in POI and NPOI this validation kicks in and throws an error that really cannot be easily circumvented.
Would you accept a PR that would check for example a global static flag, like RecordOrderer.ValidateEofOnEndOfRowBlock
which would otherwise default to true but would allow reading such files that do not fully follow the spec?
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
How to get around issue with `tail -f` not emitting EOF and ...
If you pipe the output of tail -f into a program that reads the whole input before it starts emitting output, the program...
Read more >Checking for EOF and skipping lines in java
I am trying to read from a text file and use the input to create multiple different objects. I obviously don't want to...
Read more >MOVE-TO-EOF( ) method - Progress Documentation
MOVE-TO-EOF( ) method ... Moves the cursor position in an editor to the end of the current text. Return type: LOGICAL. Applies to:...
Read more >Problem with BULK COLLECT with million rows - Ask TOM
Hi, We have a requirement where are supposed to load 58 millions of rows into a FACT Table in our DATA WAREHOUSE.
Read more >VALIDATE statement - Progress Documentation
Verifies that a record complies with mandatory field and unique index definitions. Syntax VALIDATE record [ NO-ERROR ] record The name of the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@tonyqus there are errors in the specs and errors in plenty of third party software, so it’s generally best to start with Excel’s behavior. Attached is a sample BIFF5 XLS file generated using SheetJS https://jsfiddle.net/bk3pjs74/
BIFF5 file: npoi776.xls
To see a BIFF8 version of this, the library has to be patched to remove the current Window2 write call:
BIFF8 file: npoi776.biff8.xls
Both files pass Microsoft’s Binary File Format Validator and open in Excel 2019 for Windows and for Mac. It’s reasonable to assume spec error.
PS: From our old test machine, the program files have the following checksums:
Can you create a PR for this? I think I can review the code. @lahma