Open GoogleCodeExporter opened 9 years ago
I've attached changes I made a while back to fix a similar (very likely the
same) issue. These changes were in addition to the changes mentioned in Issue
31. The attached file is the Encode directory (Office -> Excel ->
BinaryFileFormat -> Encode). Compare them to your's to see what I changed. See
WorkbookEncoder.EncodeWorkbook() and WorkSheetEncoder.Encode().
Hope this helps.
Original comment by mrjames...@gmail.com
on 28 Sep 2012 at 8:41
Attachments:
For me issue is not solved.. I am using Windows 7, Office 2010
Original comment by raghukal...@gmail.com
on 30 Oct 2012 at 1:17
For me there is the same problem after changes related to Issue 31 and current
Issue 137. I m with Windows 7 64 bit, Office 2007.
Original comment by Bis...@abv.bg
on 6 Nov 2012 at 8:33
Still same problem.. It does'nt work like what I expected..
Original comment by kyunga...@gmail.com
on 13 Nov 2012 at 12:44
That is relative to missing codepage.
Just insert those lines:
CODEPAGE codepage = new CODEPAGE();
codepage.CodePageIdentifier = (ushort)1200;
records.Add(codepage);
above WINDOW2 window2 = new WINDOW2();
in WorkSheetEncoder.cs
Original comment by com.fl...@gmail.com
on 14 Dec 2012 at 10:23
I have made everything discribed here: first I have made changes from Issue 31,
after that begun the validation problem, next I have made changes described in
current Issue 137, but problem still persist! I use Windows 7 64 bit, Office
2007 and Office 2010 but and with both when I try to open Excel file a message
is appeared - "Security Alert - Office File Vilidation". Please help! I attach
my WorkSheetEncoder.cs file.
Original comment by Bis...@abv.bg
on 21 Jan 2013 at 8:38
Attachments:
This file validation still occurs, even with the issue 31 and issue 137 fixes
in the library. Please address this!
Original comment by adam.ham...@gmail.com
on 9 Apr 2013 at 6:44
See issue 31.
I sent the corrected window2.sc
Original comment by marek.le...@gmail.com
on 9 May 2013 at 8:39
[deleted comment]
I can use it without problem.
I changed Window2.cs and followed as mentioned on Issue 31.
Really thanks a lot!
Original comment by kyunga...@gmail.com
on 11 Oct 2013 at 6:02
@kyunga...@gmail.com
Could you please send me latest dll which resolved this warning Issue
Original comment by kumar...@googlemail.com
on 29 Apr 2015 at 11:19
You're welcome :-)
Original comment by Bis...@abv.bg
on 8 May 2015 at 2:35
Attachments:
Original issue reported on code.google.com by
kyunga...@gmail.com
on 18 Jul 2012 at 1:40