None of the workbooks have passwords but all are protected (without a
password).
Thanks in advance.
If it has, try closing other applications/workbooks. The maximum number of
sheets in any workbook is limited by available memory.
If that doesn't help, I'd try this against a copy of the workbook. See if you
can remove worksheets. If you can, then see if you can add more after you've
deleted a few.
--
Dave Peterson
Close excel
Windows start button|Run
type:
excel /safe
Then use file|open to open your file, can you delete/insert sheets?
If yes, then maybe you have a macro that's disabling those options.
--
Dave Peterson
"None of the workbooks have passwords but all are protected (without a
password)."?
If a workbook is protected, you cannot insert sheets.
Gord Dibben MS Excel MVP
The Excel File itself it NOT password protected. You don't need a
password to open it. The workbook IS protected from
TOOLS,PROTECTION,PROTECT SHEET. The workbook has been UNPROTECTED in
that sense. The other 3 workbooks are basically clones of each other.
the only difference between them is the data that is stored in them.
IOW, I create one workbook and save it 4 times to get each school
their own file to track inventory (food items).
Hope that helps.
thanks for the suggestion. I went back to last year version and
modified it for this year to get around the problem. Everything is
fine now though am still puzzled as to why just that one workbook is
failing.
Thanks for the suggestions...
On Sun, 01 Aug 2010 06:08:18 -0500, Dave Peterson
You've seen the file level password to open (or password to modify).
You've see worksheet level (Tools|protection|protect sheet)
But it also offers a workbook level protection:
Tools|Protection|protect workbook
And there's an option to protect the workbook's structure in that last type.
You may want to look for this type once more.
--
Dave Peterson
That was the problem. The entire workbook was protected.
I generally use ASAP Utilities function to PROTECT and UNPROTECT the
sheets. I'm assuming this one workbook was somehow PROTECTED using
TOOLS instead.
Thanks for all your trouble solving this problem.
On Mon, 02 Aug 2010 13:39:21 -0500, Dave Peterson