Auto-Calc issue

Originally Posted by curiouscat408

@Russ.... Can you remove the "[SOLVED]" tag for the thread, since the problem has not, in fact, been solved to your satisfaction?



.... When you do what, or when what happens?!

Do any of your VBA modules "temporarily" set Manual mode?

And do you have any third-party VBA code?

My guess is that some VBA code accidentally leaves the calculation mode in Manual when it terminates or aborts.

Post #1 marked unsolved.

This occurs every time I open the WB. IE, I can go to the menu bar, set calcs to auto, close the WB, reopen the WB and it shows set back to manual. Getting late here so I'll try your debugging tips tomorrow, thanks!

No manual calc set anywhere in any code.

No 3rd party add-ins at all. I do have this date picker, but it only gets called by a button placed on the main WS, and I've avoided doing that while trying to figure this out.

I've also "compiled" the VBA code (never knew what that did until snooping around here!) and it throws no errors.

Any insight on that debug window as far as event order? Looks like the iterated WS_Calculate events are running first, then the macro "borders", finally WB_Open. Is that the correct order in the immediate window or am I backwards?

Thanks!

Russ

Originally Posted by RASelkirk

I'll try your debugging tips tomorrow

Probably no need, based on the following.

-----

Originally Posted by RASelkirk

This occurs every time I open the WB. IE, I can go to the menu bar, set calcs to auto, close the WB, reopen the WB and it shows set back to manual.

When you "set calcs to auto, close the WB", do you get prompted to "save" or "don't save"? And if so, which do you choose?

Assuming that you choose "save", I would guess that there is a problem in the Workbook_Open (or Auto_Open) and/or the Workbook_BeforeSave code path.

If you do not have either procedure, and even if you do, if you truly do not set Application.Calculation anywhere in your code or in third-party code, I'm afraid that I have run out of ideas, and I will not be able to help you.

I would start stripping away functionality until (if) the problem goes away.