Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I am working in an environment where certain spreadsheets are password
protected, but the developers do not know the passwords. Even if we did, writing them into the code would be against policy as well. For now, we are running Excel 2000. Our code can modify password-protected sheets by setting UserInterfaceOnly = True, which does not require a password. What about when we move to Excel 2002? Setting UserInterfaceOnly will no longer work for us since we cannot provide a password. Is there an alternative in Excel 2002 that will allow the code to make changes to the spreadsheets that the end-user is not allowed to make? Thanks! Lee |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Excel 2000 versus 2003 and the TEXT Function | Excel Worksheet Functions | |||
Excel 2003 versus 2002 seem incompatible related to the EDATE fun. | Excel Worksheet Functions | |||
VBA and 2002/2003/2000 | Excel Programming | |||
Excel 2000 versus Excel 2002 question | Excel Programming | |||
Macros i XL 2003 versus 2000 - speed problems | Excel Programming |