I have a stack of code running in a spreadsheet or two. The workbooks and sheets are protected but they are open to allow VBA to make changes. So far so good.
I have the following draft giving me problems though.
Runs just fine when unlocked etc. But if it is locked up I get "Application-defined or object-defined error". What am I missing?
Please Login or Register to view this content.
The macro will have to unprotect and then protect the sheet. Change the password (in red) to suit your needs.
Please Login or Register to view this content.
You can say "THANK YOU" for help received by clicking the Star symbol at the bottom left of the helper's post.
Practice makes perfect. I'm very far from perfect so I'm still practising.
I really wanted to avoid that. Besides I'm a bit confused when after opening the workbook (and once again since to make sure of it) the following code has been run.
wsh is just the holder for all sheets to be cycled through. This allows all other code re style changes, content changes etc to be made by code so why not this particular bit of code?Please Login or Register to view this content.
Last edited by malcmail; 07-31-2019 at 10:11 AM.
Even unlocked the code is not working now. Swear I'll never understand the oddities of VBA! Ignore that - that was down to idiot. But the original issue still remains.
The UIO parameter is not 100% reliable. For some things you still may have to unprotect and reprotect, which is a real pain in more recent versions as that's a lot slower than it used to be. Of course, that's not an issue for you on 2003...
Rory
It now runs twice. Once on opening, once on pressing a start button. All other choice works ok so why would this bit take exception? Oh we've moved on now. No more 2003, so now we can actually do stuff (just not always quickly)Originally Posted by rorya
The UIO parameter is not 100% reliable. For some things you still may have to unprotect and reprotect, which is a real pain in more recent versions as that's a lot slower than it used to be. Of course, that's not an issue for you on 2003...
You might want to update your profile then.
As to why it takes exception, as I said, that parameter is just not 100% reliable.
Good point - I'll get that changed.
I think I have found the culprit though. Need to add "DrawingObjects:=True," to the protection line - seems to work OK then.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks