M
Mike J
This problem occurs when I protect a document using a
macro 4.0 function: =PROTECT.DOCUMENT(TRUE,,,TRUE,TRUE).
When I use the function within a macro4.0 macro, on an
original file, everything works fine. The sheet has
unlocked cells, and when the sheet is protected, it
allows me to access those cells. But if I save the file,
or save.as another name, then the fun begins.
The enable selection of the sheet( view codes) has gone
from 0-xlNoRestrictions to -4142- xlNoSelection. This
locks me out of doing anything in the sheet. When I
unprotect and then re-protect the sheet using the
Tools
rotection menu, when I re-protect it, the standard
check marks for select locked cells, select unlocked
cells, are MISSING.
IS THIS A BUG IN THE CODE REGARDING MACRO 4.0 function
PROTECT.DOCUMENT and the new protection function options
in Excel 2002? If so, How can I make it work? The macros
I use constantly protect and unprotect sheets.
I know Macro 4.0 very well, but Visual Basic for
Applications, I have little knowledge. But if there is a
fix utilizing Visual Basic, I'll take it.
Any suggestions, please let me know.
macro 4.0 function: =PROTECT.DOCUMENT(TRUE,,,TRUE,TRUE).
When I use the function within a macro4.0 macro, on an
original file, everything works fine. The sheet has
unlocked cells, and when the sheet is protected, it
allows me to access those cells. But if I save the file,
or save.as another name, then the fun begins.
The enable selection of the sheet( view codes) has gone
from 0-xlNoRestrictions to -4142- xlNoSelection. This
locks me out of doing anything in the sheet. When I
unprotect and then re-protect the sheet using the
Tools

check marks for select locked cells, select unlocked
cells, are MISSING.
IS THIS A BUG IN THE CODE REGARDING MACRO 4.0 function
PROTECT.DOCUMENT and the new protection function options
in Excel 2002? If so, How can I make it work? The macros
I use constantly protect and unprotect sheets.
I know Macro 4.0 very well, but Visual Basic for
Applications, I have little knowledge. But if there is a
fix utilizing Visual Basic, I'll take it.
Any suggestions, please let me know.