Worksheet Protection (MS Excel 2003)

Topic

New Reply

I am having a problem with workbooks where I have enabled worksheet protection. I have a workbook with 2 worksheets. The first worksheet contains raw data. The second worksheet has tables with equations referencing the the first worksheet. I have created charts and graphs on the second worksheet referencing the calcuation tables.

I have locked all of the cells of the second worksheet and only enabled editing/reformatting of the charts and graphs with the protection function.

After going in and out of the workbook many times–and many users later–the protection function in the Tools menu seems to be disabled now, but only for the second worksheet. I cannot select Unprotect worksheet and enter my password to enable full editing of the worksheet. Have I stumbled upon a Microsoftism? Have you heard of such a thing?

Unfortunately, the workbook is on another domain and I can’t transfer it here for posting. Please help.

Amy

Reply | Quote

Replies

Has the workbook been made shared recently? If so, you should see [Shared] in the title bar after the name of the workbook.
You cannot protect or unprotect a worksheet in a shared workbook. You must stop sharing in order to do so.

Reply | Quote

The workbook has not been made shared recently. No [Shared] in the title bar after the name of the workbook.

I was playing with it and chalk it up to a Microsoftism. I restarted my computer and that didn’t help. I opened the workbook again, clicked on the unresponsive worksheet, right clicked to View Code, did nothing and exited the View Code and the Protection function essentially reset so that I could select Unprotect Worksheet and type my password. Ridiculous. What’s up with that?

Reply | Quote

That’s puzzling, I have no explanation…

Reply | Quote

Do you have any code that runs in the background which unprotects and reprotects (triggered by some event)?

If the code wasn’t run until the end and completed the sheet would be unprotected and not protected and then if the event was triggered again and run until the end, it would ultimately get protected again. Just an idea

Steve

Reply | Quote