The Tamer
Well-known Member
- Joined
- Jun 10, 2004
- Messages
- 520
Hi all
A while ago I got a lot of code to find out if a workbook was read-only or not, then to super-protect the read-only versions so that "SaveAs" couldn't be used to replace the read-write version. I did stuff like removing copy and past, and the 'file' and 'tools' menus were disable. On closing a read-only version, all of it was enabled and protection was taken away.
I've just found a problem in my code! When a user presses "notify" after the workbook is opened read-only, and then opens the read-write version when he is prompted to do so, the new read-write version still keeps some of the protected characteristics of the read-only version.
Once it is closed, all future versions behave like the read-only versions until i go through the process of painstakingly fixing the WB.
Any ideas as to why "notify" might be causing the problem, and any workarounds?
Ta very much
Tamer
A while ago I got a lot of code to find out if a workbook was read-only or not, then to super-protect the read-only versions so that "SaveAs" couldn't be used to replace the read-write version. I did stuff like removing copy and past, and the 'file' and 'tools' menus were disable. On closing a read-only version, all of it was enabled and protection was taken away.
I've just found a problem in my code! When a user presses "notify" after the workbook is opened read-only, and then opens the read-write version when he is prompted to do so, the new read-write version still keeps some of the protected characteristics of the read-only version.
Once it is closed, all future versions behave like the read-only versions until i go through the process of painstakingly fixing the WB.
Any ideas as to why "notify" might be causing the problem, and any workarounds?
Ta very much
Tamer