Thanks Yegor, unfortunately this file wasn't generated by a macro. I
just copied the sheet from another file with Excel.

But there never were 3700 columns in use. I don't know why excel
generates this. But shouldn't POI read the file as well without having a
problem?

Br, Michael

schrieb Yegor Kozlov:
> How did you create this file? Was it a VB macro or what ? At first
> glance the problem is in the code that loads column information and
> XSSF stumbles on this file because there are more than 3700 columns on
> the first worksheet.
> 
> Yegor
> 
> On Tue, Jan 10, 2012 at 9:19 PM, Michael Langhans
> <[email protected]> wrote:
>> Hello,
>>
>> I encountered a problem with an Excel2007 OOXML file generated using
>> Office 2010. When opening the Workbook it just doesn't finish. CPU goes
>> to 100% and nothing more happens (despite my cpu working).
>>
>> I also had a look into the file and found that there are a lot of "rows"
>> which seem to contain format data.
>>
>> I'm not sure on what to do? Attached is a file that will have this
>> problem. And also here is a list what I did:
>>
>> - use POI 3.8 Beta 5 (no difference)
>> - resaving the file using previous Excel Versions (did resolv the problem)
>> - running Excel2010 file cleanes (Excel Menu -> Prepare) (no difference)
>>
>> Can anybody help me?
>>
>> I used the following lines for loading:
>>
>> BufferedInputStream fstream = new BufferedInputStream (new
>> FileInputStream(outputFile));
>> Workbook ourWorkbook = new XSSFWorkbook(OPCPackage.open(fstream));
>>
>> Thanks in advance and best regards,
>> Michael
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to