Protected View Issue (Delaying Code execution?)

[MPW]

Been chasing this rabbit for years.
When my very heavy macro-ed workbook has a name change, Excel will prompt me to "Enable Editing" upon opening the workbook.
I will then get a debug of some variation of this:

I will then end the routine, close the workbook without saving it. When I reopen it, it will operate correctly until it is renamed again. rinse and repeat.

For some time this would only occur on my pc. Since I have several macros activating when the workbook is opened, I chalked it up to a code execution hold up while I enabled the workbook.
My problem is that since my last code update, this has been effecting other users. As I said, after they initially open and close the workbook, it will run fine from then on.

I understand that I probably caused this problem. My question is if there is some methods of either halting the code until the content is enabled or some method ignore the errors the first time around. and no, I do not want to use "On Error Resume Next".

One last thing, I do not use "Save As" when renaming this workbook. We found that by doing this method it continually increased the size of the workbook. We rename it using Window Explorer.

Thank you for considering this matter. I defer to the wisdom from abroad!

 

[MPW]

I agree that you should not be able to bypass the protected view dialog. My problem arises from the fact that the objects are not loading even after they enable editing. The objects are not loaded until after the workbook object sub is manually stopped in the vba editor.