search

Zoumaho / excellibrary

Automatically exported from code.google.com/p/excellibrary
0 stars 0 forks source link

Problem to open up .xls file on Office 2010 #60

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Use your ExcelLibrary.WinForm application
2. Create test xls with it.
3. Try to open it up in Excel 2010

What is the expected output? What do you see instead?
Excel found unreadable contant in newdoc.xls. Do you want to recover the 
contents of this workbook? If you trust the source of this workbook, Click yes.

What version of the product are you using? On what operating system?
Windows 7 Enterprise x64 / Office 2010 Professional Plus, newest version from 
here.

Please provide any additional information below.

Original issue reported on code.google.com by evotect...@gmail.com on 4 Jul 2010 at 2:55

GoogleCodeExporter commented 9 years ago 
I've tried changing the target CPU to x86 but that appears to make no 
difference.

I'm running Excel 2007 on Windows 7 x64.

Original comment by hamilton...@gmail.com on 6 Jul 2010 at 3:45

GoogleCodeExporter commented 9 years ago 
Excel 2007 works fine. Excel 2010 has problem.

Original comment by evotect...@gmail.com on 6 Jul 2010 at 5:30

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I have also duplicated this problem, opening the xls file Excel 2007 in Windows 
7 x64.

Original comment by RDOdontplay on 29 Jul 2010 at 6:20

Attachments:

GoogleCodeExporter commented 9 years ago 
I can confirm I am running windows 7 x32 and I get the same error message.  If 
I forward it to a co-worker whom is running Windows XP, he can open the file 
with no errors.  We are both running Office 2007 Std Edition.

Original comment by jxko...@gmail.com on 25 Aug 2010 at 1:15

GoogleCodeExporter commented 9 years ago 
I also have this problem. Windows 7 x86. Office 2010. Opens perfectly in Open 
Office.

Original comment by blackby...@gmail.com on 22 Sep 2010 at 7:43

GoogleCodeExporter commented 9 years ago 
Same issue, Not able to open the file with 2010, it gives a notification with 
2007 but however manage to open..

Original comment by addicted...@gmail.com on 25 Sep 2010 at 7:57

GoogleCodeExporter commented 9 years ago 
I have the same problem and maybe found a workaround: I appended some empty 
rows so that there were at least 20 rows and the filesize was at least 7kB. 
Then Excel (2010, on win7 64bit) could read the file.

Original comment by hdkest...@gmail.com on 8 Oct 2010 at 9:02

GoogleCodeExporter commented 9 years ago 
I confirmed this bug, as well as the fix to add 20 rows. Thank you.

Original comment by Jay.Pomp...@gmail.com on 27 Oct 2010 at 6:11

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Hi,

I confirmed this bug using the sample code on the project site 
(http://code.google.com/p/excellibrary/).

Adding 75 additional rows to the sample code (which brought the file size up to 
7kb) fixed the issue for me.

Thanks.

Original comment by nickmoo...@gmail.com on 29 Oct 2010 at 10:12

GoogleCodeExporter commented 9 years ago 
On Windows7 x64 Excel2010, I get "Excel found unreadable content in 
'MyExcelFileExcelLibraryDataSetHelper.xls'. Do you want to recover the contents 
of this workbook?  If you trust the source of this workbook, click Yes."  Then 
I click Yes, and the document does not load.

Original comment by Konigm...@gmail.com on 3 May 2011 at 8:09

GoogleCodeExporter commented 9 years ago 
When I made a sheet with 100 rows of Numbers, it was large enough to work, when 
I made a sheet with 99 rows of Numbers, it gave the "Excel found unreadable 
content" warning.  When I added a second column of numbers it would wok with 
only 61 rows, but not with 60 rows.  (I'm using DataSetHelper.CreateWorkbook(), 
so the first row is always the string of the column labels)

Original comment by Konigm...@gmail.com on 3 May 2011 at 9:07

GoogleCodeExporter commented 9 years ago 
The problem is actually in the FAT table.
first record should not be 0xfffffffd

Count = 0x00000080
    [0x00000000]: 0xfffffffd
    [0x00000001]: 0xfffffffe
    [0x00000002]: 0x00000004
    [0x00000003]: 0xfffffffe
    [0x00000004]: 0xfffffffe
    [0x00000005]: 0xffffffff
    [0x00000006]: 0xffffffff

Original comment by linobarr...@gmail.com on 13 May 2011 at 10:50

GoogleCodeExporter commented 9 years ago 
btw, you can replicate it with an empty workbook too.
(attached file)

Original comment by linobarr...@gmail.com on 13 May 2011 at 10:55

Attachments:

GoogleCodeExporter commented 9 years ago 
Hello guys,I'm having the same problem, but I dicovered a workaround to fix 
this problem. In my opinion, it's bizzar. The major problem is the output file 
is too small, less than 10KB. So, if you increment your sheet with more lines 
and columns with a space, you'll be able to open the file normally.

Best regards.
Marcos Yano

Original comment by marcos.y...@gmail.com on 13 Jun 2011 at 5:40

GoogleCodeExporter commented 9 years ago 
My workaround was to switch to NPOI
http://code.google.com/p/npoi/

Original comment by Konigm...@gmail.com on 13 Jun 2011 at 5:58

GoogleCodeExporter commented 9 years ago 
Has anyone a Bugfix for this yet?

Original comment by jochen.k...@googlemail.com on 5 Jul 2011 at 12:02

GoogleCodeExporter commented 9 years ago 
Can confirm this is still present and causing problems here.
If flood to over 7k then loads fine in Excel2010, less than this and still get 
unreadable content error. Same XLs loads fine in Excel2003.

Original comment by colk...@freenetname.co.uk on 9 Nov 2011 at 10:26

GoogleCodeExporter commented 9 years ago 
This is still present in my case as well.

Original comment by Nikita1984 on 7 Dec 2011 at 5:01

GoogleCodeExporter commented 9 years ago 
Ok, I had the same issue. 

My solution:

I inserted 200 empty rows, then the file is bigger than 10 kb, now it's working 
fine. 

Thanks everyone.

Original comment by ehite...@gmail.com on 25 Jan 2012 at 3:24

GoogleCodeExporter commented 9 years ago 
Yes, comment 24 is right, I also inserted 200 empty rows... then the file is 
correct.

Original comment by programt...@gmail.com on 11 May 2012 at 1:19

GoogleCodeExporter commented 9 years ago 
BUT: if I open a "large" 500KB excel file, and just save it (whithout any 
modification), the result: The file is unreadable...

Original comment by programt...@gmail.com on 11 May 2012 at 1:29

GoogleCodeExporter commented 9 years ago 
Issue 131 has been merged into this issue.

Original comment by jetcat on 1 Mar 2013 at 10:59

GoogleCodeExporter commented 9 years ago 
Same problem on Window 7 for Office 2010.
File is corrupt while in OpenOffice it works perfectly.

After adding 100 rows and save it for the > 20kb size, I ended with a size of 
8KB and now works in Office 2010.

A fix for this is nice to have but not necessary for me.

Thanks for the great plug-in!

Original comment by larsrotg...@gmail.com on 23 Oct 2013 at 5:42

GoogleCodeExporter commented 9 years ago 
is there any way to fix this problem without hacking the system and adding 75 
empty rows. Any help would be greatly appreciated.

Original comment by cesar.bo...@gmail.com on 22 Jan 2014 at 7:57

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
funciona agregando mas filas o agregando otra tabla con filas vacias.
http://www.codeproject.com/Tips/313731/How-to-convert-DataSet-to-Excel-workbook-
xls-using

http://msdn.microsoft.com/es-es/library/system.data.datatable.newrow(v=vs.110).a
spx

Original comment by davidc1...@gmail.com on 10 Sep 2014 at 4:40

GoogleCodeExporter commented 9 years ago 
I can open this file on Window 7 for Office 2010,
After adding a loop with random text, make capacity bigger 10KB, you can open 
it.

Original comment by letruong...@gmail.com on 22 Sep 2014 at 6:03