Hi, just ran into this one.
Apparently Excel 2016 throws a fit and shows an Error dialog Box with the (helpful?) message "400" if your VBA code is making changes to a protected sheet.
The resolution in my case was:
I suppose to be fair to M$, this is kinda a change for the better as it preserves the integrity of a protected sheet; however an error dialogue that only displays "400" is just plain lazy and needs fixed.
Please Login or Register to view this content.
If it'd make you feel better using my answer because of my street cred, then you can go ahead and clickAdd Reputation below to improve it.
if the sheet is unprotected, why would it throw an error?
the work around was to: unprotect, change, reprotect... which the code did not need to do prior to Excel 2016Originally Posted by Gregor y
Last edited by Gregor y; 03-20-2018 at 02:37 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks