perola.rike
Board Regular
- Joined
- Nov 10, 2011
- Messages
- 151
Our hospital use a .xlsm WB that most of the time only opens as write-protected on the hosputal computers. I cannot figure out how to solve this. Some facts about the sheet and the troubleshooting I've done (other macroactivated WB opens properly - so there must be something wrong with this particular WB(?)):
WB-Facts:
- The WB contains a lot of formulas, functions, userforms and a lot of vba code
- The WB are restricted to the hospital domains with workbook_open code like this:
If Environ("USERDOMAIN") <> "HOSPITALS_DOMAIN" Then Call ThisWorkbook.Close(SaveChanges:=False)
- The problem seems to vary to some extent between different computers, but no systematic difference have been detected (old vs new computers, laptop vs stationary desktop computers)
- The computers run Win7 and the users have no administrator permissions (hospital security restrictions), cannot install anything on the computers
- It runs Excel 2007
- Other hospitals do not have the same issue.
Troubleshooting:
- Other .xlsm WBs opens properly, even those restricted with workbook_open code (see code above)
- The .xlsm sheet opens as write-protected both when opened from a server and local destinations (c:, desktop etc) - so this might not be the issue
- I have unhooked all possible macro security options in e.g. excel security Trustcenter (I think)
- The problem persists even when the Workbook_open code is removed
- The write-protection issue might dissapear for some time, then suddenly it returns and persists for a while, then it opens properly again - have found no systematic pattern here
- There are no simultaneously users
Any suggestions to solve this frustating issue are very appreciated!
I'll gladely provide more detailed information if needed.
WB-Facts:
- The WB contains a lot of formulas, functions, userforms and a lot of vba code
- The WB are restricted to the hospital domains with workbook_open code like this:
If Environ("USERDOMAIN") <> "HOSPITALS_DOMAIN" Then Call ThisWorkbook.Close(SaveChanges:=False)
- The problem seems to vary to some extent between different computers, but no systematic difference have been detected (old vs new computers, laptop vs stationary desktop computers)
- The computers run Win7 and the users have no administrator permissions (hospital security restrictions), cannot install anything on the computers
- It runs Excel 2007
- Other hospitals do not have the same issue.
Troubleshooting:
- Other .xlsm WBs opens properly, even those restricted with workbook_open code (see code above)
- The .xlsm sheet opens as write-protected both when opened from a server and local destinations (c:, desktop etc) - so this might not be the issue
- I have unhooked all possible macro security options in e.g. excel security Trustcenter (I think)
- The problem persists even when the Workbook_open code is removed
- The write-protection issue might dissapear for some time, then suddenly it returns and persists for a while, then it opens properly again - have found no systematic pattern here
- There are no simultaneously users
Any suggestions to solve this frustating issue are very appreciated!
I'll gladely provide more detailed information if needed.