Bug 150193 - Protect spreadsheet structure does not work with excel and vice versa
Summary: Protect spreadsheet structure does not work with excel and vice versa
Status: RESOLVED DUPLICATE of bug 122922
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.3.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-29 08:40 UTC by Gauthier
Modified: 2022-08-04 21:23 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gauthier 2022-07-29 08:40:42 UTC 
There seem to be a general incompatibility regarding protecting spreadsheet structure between LO and Excel. 

If I create a .ods file with LO and protect the spreadsheet structure, then open the same file in Excel 2019 or 365, then it tells me the file is protected with a password and cannot open it. 

If I save the file in LO as .xlsx and open it in Excel, it opens with the structure is not protected any longer (I can hide and unhide sheets).

If then I protect the structure of the .xlsx file with Excel and open it in LO the structure is not protected (but it is protected in Excel). If I do nothing but just save the file again with LO (still as .xlsx) and open it in Excel the structure protection is lost again.

Sheet protections work as expected and is conserved between LO and Excel.

Using LO 7.3.4 on Linux - KDE Neon.
Comment 1 m_a_riosv 2022-07-29 14:51:44 UTC 
Repro
Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: eea7038c182cc1f6cd792359053ea2561a200026
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL
Comment 2 Timur 2022-08-03 06:51:14 UTC 
Rule of thumb is search before reporting and confirming. 
Duplicate of bug 122922 and bug 143333, as proper is to report separately.

*** This bug has been marked as a duplicate of bug 122922 ***
Comment 3 m_a_riosv 2022-08-04 21:23:50 UTC 
(In reply to Timur from comment #2)
> Rule of thumb is search before reporting and confirming. 
> Duplicate of bug 122922 and bug 143333, as proper is to report separately.
> 
> *** This bug has been marked as a duplicate of bug 122922 ***

Better not answer to you.