Contact
12 programs
Explore the site

Apache OpenOffice Calc Compatibility and Migration Decisions

XLSX opening is not XLSX saving

The official Apache OpenOffice 4.1 Calc Guide states that Calc can open XLSX files but cannot save in XLSX format. It documents XLS as an Excel-format exchange option. Do not promise an XLSX return file simply because the incoming XLSX opens. See the directly checked Load/Save options and Excel-format saving instructions.

This reference concerns the free Apache OpenOffice desktop suite, 4.1 guide scope, checked on 2026-10-21. It is not LibreOffice documentation and not a new native conversion test. Record the actual installed build, operating system and receiving application before testing. Documentation of an input format is not evidence that every workbook using it will import faithfully.

Agree on the deliverable first

Ask the workbook owner what the recipient needs to do, not just which extension they normally use:

  • If the recipient accepts ODS, test an ODS working copy in their application and keep the original separately.
  • If the recipient requires XLS, agree on that legacy format explicitly, then test the actual workbook features after export. Do not label an XLS file as XLSX.
  • If the recipient insists on XLSX, this documented OpenOffice route does not satisfy the requirement. Keep that migration blocked until an authorized, separately tested route is agreed; do not overwrite or rename the original to conceal the mismatch.
  • If the recipient only needs a visual report, decide whether a fixed PDF is sufficient rather than sending an editable workbook. Follow the printing and PDF tutorial and verify the resulting pages.

A different format is an agreed change to the deliverable, not an automatic workaround. A file that opens but loses a required formula, linked source or editable object has not met the requirement.

Keep three roles separate

Keep the incoming original unchanged. Save a separately named ODS working master before making an exchange copy. Use another filename for the output destined for review.

The official Save As guide warns that non-native formatting may change and that subsequent edits apply to the newly selected file, not automatically to the ODS version. Reopen the working master deliberately when continuing work there. A single filename reused for original, working copy and delivery makes rollback and comparison harder.

Inventory required sheets, formulas, names, validation, charts, macros, external references and printed outputs. Record an expected result or behavior for each essential item. Treat untested automation as a hold rather than enabling unfamiliar code. For external dependencies, the existing linked-workbook guide explains a separate problem that a correct grand total alone cannot rule out.

Try a small acceptance exercise

In a practice workbook enter B2 = 5, C2 = 7, B3 = 2 and C3 = 9. Put =B2*C2 in D2, =B3*C3 in D3 and =D2+D3 in D4. Independently calculated results are 35, 18 and 53.

Record those expectations before saving a separately named exchange copy in the agreed format. Reopen that copy and inspect both formula expressions and results. Change B3 to 3: D3 should become 27 and D4 62. Restore B3 to 2 and confirm 53. Save, close and reopen again. Repeat in the actual receiving application if that is part of the delivery.

These are proposed checks, not newly observed OpenOffice results. Use a record with columns for stage, application/build, expected result, actual result and status. Keep unperformed stages marked Not tested. Then add controls for the real workbook’s essential features; this exercise does not validate macros, chart editing or complex formatting.

Decide what to do with a mismatch

If the receiver rejects the file format, return to the deliverable agreement before repairing cells. If a formula gives a plausible but wrong answer, check its expression and inputs; see recalculation and circular formulas. If only the printed layout differs, compare the agreed PDF or print output separately from numerical accuracy.

Accept only the exact workflow and versions tested. Keep the original, working master and review record until the owner confirms the result meets the agreed requirements. No new application screenshot, export or recipient-side test is claimed here.