Re: All my POI built Excel files are suddenly corrupt?

I really don't think the POI community can answer questions like this. I wo=
uld contact Microsoft. They get paid to answer support questions. POI volun=
teers don't.

It is no shock that different versions of Excel don't work exactly the same=
. Or that other products that can read and/or write xlsx files could also h=
ave differences. If Microsoft really cared, there would have a compliance s=
uite that product maintainers could use to see if their products as they sh=
ould.

Have you tried=C2=A0Zip64Mode.Never or=C2=A0Zip64Mode.AsNeeded? If you don'=
t write a very large xlsx files,=C2=A0Zip64Mode.Never should be ok.






On Tuesday 5 November 2024 at 13:28:19 GMT+1, Andreas Reichel <andreas@mant=
icore-projects.com> wrote:=20





Dear All,

this is still an issue. We got complains from a customer using MS Excel
2016 that now all the Excel files are corrupted and can NOT be
repaired. So what we have now is:

- Zip64Mode.Always works with MS Excel 2016, but shows corruption with
LibreOffice (although that will be repaired automatically)

- Zip64Mode.AlwaysWithCompatibility shows corruption with MS Excel 2016
(can not be repaired?), but works flawlessly with LibreOffice

All other programs like Gnumeric and GoogleSheets always worked.

What would be the best way to test on various Excel versions? Is only
2016 affected? (I don't know where to get an Excel from for testing.)

Best regards
Andreas





On 2024/11/02 00:52:53 Andreas Reichel wrote:
> Good Morning All.
>
> Unfortunately we seem to have celebrated too early since we get now
> reports from one single MS Excel user about corrupted files.
> And now things become really messy:
>
> 1) what was the best way to test Excel files on Excel (various
> versions?)=C2=A0
> 2) why all of this just recently, what has really changed and causes
> it?
>
> Best regards
> Andreas
>
>
>
> On Mon, 2024-10-14 at 06:48 +0700, Andreas Reichel wrote:
> > On Fri, 2024-10-11 at 10:30 +0000, PJ Fanning wrote:
> > > The SXSSF default is Zip64Mode.Always.=C2=A0
> >
> > Greetings,
> >
> > we have migrated everything to =C2=A0Zip64Mode
[1]=C2=A0AlwaysWithCompatibility
> > [2]=C2=A0and this has solved our problem entirely.
> > On the LibreOffice side nobody responded yet, so maybe it is safe
and
> > sound to switch POI's default Zip64Mode?
> >
> > Warm regards
> > Andreas
> >
>
>
> [1] Zip64Mode
>=C2=A0=C2=A0=C2=A0=C2=A0
https://commons.apache.org/proper/commons-compress/apidocs/org/apache/commo=
ns/compress/archivers/zip/Zip64Mode.html
> [2] AlwaysWithCompatibility
>=C2=A0=C2=A0=C2=A0=C2=A0
https://commons.apache.org/proper/commons-compress/apidocs/src-html/org/apa=
che/commons/compress/archivers/zip/Zip64Mode.html#line-50
>