I realize that "strange" isn't very descriptive - but the problem isn't easily described:
I have a nice little suite of macros, and most of them are fine. Two features of these macros, however, are pretty intense -
Excel changes after I run said features.
Excel accepts clicks, etc. - it isn't "not responding" in the crashing sense. But it isn't responsive. The sheet it shows you is usually the sheet you started from. If you click on a cell, nothing about 'the view' changes. If you type, nothing about 'the view' changes.
That said, if you save, close (all open workbooks), and reopen - the thing you typed will be on the sheet the macro made active, about where you clicked. The issue is gone.
While Excel is acting up, you can't scroll either. The ribbon is unresponsive -
Except for the file button. If you click on the file button a couple times, Excel blanks out. Mostly - here's a screen shot:
screenshot.jpg
As you can see - the font name and size are still showing. And there's a paste options icon. And the rest is white. No title bar, nothing.
If you click again, the file menu appears. If you hide that menu, Excel reappears - on the active sheet. You can scroll, update, etc. ... but sometimes it just stops, and you have to click the file menu some more.
My first thought was that Application.ScreenUpdating = True wasn't working. But running MsgBox Application.ScreenUpdating returns True.
In my search for answers, I've seen that something similar will happen when you unprotect a worksheet with VBA - a recognized bug. But these macros don't unprotect worksheets ...
Now I'm thinking it's a memory thing. An Excel limit. Unfortunately, I have to use 32 bit - we use a few other programs that interface with Excel, and they require 32 bit - so maybe Excel is just ... overloaded?
Obviously, I can have the macro save, then close all workbooks. I can tell my users with a MsgBox to reopen. I assume there isn't way to reopen via macro, as EVERY workbook must be closed at the same time to completely remove the bug - including PERSONAL.
That solution isn't ideal; I don't like leaving work for the user.
I'm really hoping someone has some ideas? Is reminded of a bug with a work-around, maybe?
I've tried:
(His problem is similar ... not quite the same ... he says a wait message before turning off ScreenUpdating solved his issue. I tried this, DoEvents ... I tried one, then both before and after turning it on ... no combination of any of that worked -)
https://www.experts-exchange.com/que...-updating.html
(His problem is also similar ... his solution (selecting a cell on the page that wasn't updating properly) didn't work for me.
http://www.ozgrid.com/forum/showthread.php?t=176432
My macros are huge (one module has 5000+ lines) and posting ALL my code here is very impractical.
(I can post more, of course ... if someone thinks that will help.)
Here's how I open:
Here's how I close:
Bookmarks