I'm writing up this pro-tip because I have seen many examples of working with protected worksheets where the code does something like this: If. VBA can not add rows to a ListObject in a protected worksheet. VBA can change the values of cells in a protected worksheet From my experience, and for this example, I can say the following is true (as a small example): I have yet to see a complete list of things VBA can do to a Protected worksheet, and things that require the worksheet to be unprotected. When UserInterfaceOnly is set to True, VBA can make certain types of changes without requiring the Worksheet to be unprotected, however a common mistake is to assume if a Worksheet was protected with UserInterfaceOnly = True, that it will still retain that setting the next time the Workbook is open.
One of the arguments that can be included when calling the Protect method of a worksheet is called UserInterfaceOnly.
0 kommentar(er)
