The reason is the stronger security in the protection, which is the same whether you do it programmatically or manually, but it isn't noticeable when you protect one sheet at a time manually. Protecting many of them programmatically compounds the problem. We have taken it to the developers already, andthey say that they added the strong security to make sheet protection stronger, and will not remove it or give us a way to opt out of it because to do that would reduce that protection. I really cannot share the exact details of the changes.
Please forgive me that I do not agree.
Another big problem if you first protect the sheets programmatically, then save them in the protected state and finally disable the ProtectWorksheets code is the following.
With some software, as e.g. Passware Kit, you can unprotect the workbook and all worksheets in seconds while that is not possible if you are protecting during the file open code, because then the workbook and all sheets are
always protected again and again with each opening of the file.
So as to me the protection is stronger when it's done prgrammatically with the workbook_open event.
I have tested this with Passware Kit and my workbook and worksheets (password protected in the way you have suggested: saved in protected state) were completely unprotected in a couple of seconds!!!
So the reason quoted from your developers (stronger protection) seems unfortunately to be a false reason. Give me back the former protection method and 1) my workbook will open faster when protected programmatically during file open code AND 2) the protection
will be stronger with this method.
Best regards
Jacques