Forum Discussion
Error "you can't change part of an array" when inserting a row in a protected sheet (Version 2401)
- Feb 23, 2024
I have no Excel 2019 to test, but yes, that could be. Build number means nothing if you compare different Excels. It means nothing as well if to compare functionality on different channels in subscription model (365).
In your question you compare Office 2019 and Excel 365 on semi-annual channel. Both have the latest on today versions
2019:
365 semi-annual:
but most probably above 365 has more functionality compare to 2019.
As for the concrete issue - 2019 has only security updates till end of the support. It works as it works, I'd don't expect any changes in behaviour for the 2019.
Hi SergeiBaklan
Thanks for trying to reproduce it. You have indeed the same Excel version.
Perhaps try with the Excel sheet itself:
https://agriculture.wallonie.be/files/20182/138111/270622%20BAF%20Attribution%20v03.02.xlsx
- SergeiBaklanFeb 21, 2024Diamond Contributor
On your file I inserted the row here
and can't insert rows in this sheet
Since both sheets are password protected don't know what's the difference in protection.
- NicWIDFeb 23, 2024Copper Contributor
Hi SergeiBaklan
Good to know it is working with your Excel version.
Note that the "insert row" is allowed only in the "Yellow part"
Unfortunately, the End user has still the problem.
His Excel version is this one:
Excel version Office 2019It is not a 365 version but an Office 2019 version.
Could it be the origin of the issue ?- SergeiBaklanFeb 23, 2024Diamond Contributor
I have no Excel 2019 to test, but yes, that could be. Build number means nothing if you compare different Excels. It means nothing as well if to compare functionality on different channels in subscription model (365).
In your question you compare Office 2019 and Excel 365 on semi-annual channel. Both have the latest on today versions
2019:
365 semi-annual:
but most probably above 365 has more functionality compare to 2019.
As for the concrete issue - 2019 has only security updates till end of the support. It works as it works, I'd don't expect any changes in behaviour for the 2019.