picklefactory
Well-known Member
- Joined
- Jan 28, 2005
- Messages
- 508
- Office Version
- 365
- Platform
- Windows
Hi folks
Just wondering if anyone else has been seeing any VBA crash issues over the past few months? We run Office 365 Business and have a fair number of WB's in network folders, the vast majority being WB's that we've run seamlessly for years with only simple VBA and nothing has changed there. Over the past few months we get random crashes/debug issues where one person tries to open a WB, and it either totally fails to run the VBA or they get a debug issue. Somebody else can open exactly the same WB on a different machine and it runs fine, once it has functioned OK on the 2nd machine, it then also runs fine again on the machine where it previously crashed. When it fails to run the VBA at all, it will also lock you out of all the code, the project library still displays all the sheets/forms/modules etc, but just ignores you if you try to view the code, no error message at all, just hangs.
If it does try and run, and we can get a debug error, it will hang on a random item of code, rarely the same thing twice, then the only two workarounds I've found are to either:
1. Stop the code running, copy whatever sub it has stuck on, delete that sub and just paste the exact same bit of code back where it was. It then runs fine.
2. Stop the code, add a random Reference library in, run the compiler, remove the temp Reference again and re-run the compiler, and all works fine.
It seems to me to be some sort of compile issue, as I think both of those methods above will force it to compile, but it rarely repeats or hangs on the same item of code. I can run a WB on my own machine a number times no problem, come to run it again and it crashes, I haven't managed to find any clue as to what could be a trigger for this seemingly random behaviour, but I really think it's a Microsoft issue.
This happens now on, I think, all of our macro enabled WB's, I've checked all the permissions (Which haven't changed anyaway), Trust centre settings etc, our IT team manage Win updates. There is definitely nothing wrong with the code, as these are long proven WB's, and it has now affected so many.
I've been aGoogling and I'm finding numerous similar questions raised on the MS Community without yet being able to find a definitive cause or fix, so being as it seems to be an issue affecting Excel specifically, I thought I'd ask here with so many users to see if anyone else is seeing it?
Just wondering if anyone else has been seeing any VBA crash issues over the past few months? We run Office 365 Business and have a fair number of WB's in network folders, the vast majority being WB's that we've run seamlessly for years with only simple VBA and nothing has changed there. Over the past few months we get random crashes/debug issues where one person tries to open a WB, and it either totally fails to run the VBA or they get a debug issue. Somebody else can open exactly the same WB on a different machine and it runs fine, once it has functioned OK on the 2nd machine, it then also runs fine again on the machine where it previously crashed. When it fails to run the VBA at all, it will also lock you out of all the code, the project library still displays all the sheets/forms/modules etc, but just ignores you if you try to view the code, no error message at all, just hangs.
If it does try and run, and we can get a debug error, it will hang on a random item of code, rarely the same thing twice, then the only two workarounds I've found are to either:
1. Stop the code running, copy whatever sub it has stuck on, delete that sub and just paste the exact same bit of code back where it was. It then runs fine.
2. Stop the code, add a random Reference library in, run the compiler, remove the temp Reference again and re-run the compiler, and all works fine.
It seems to me to be some sort of compile issue, as I think both of those methods above will force it to compile, but it rarely repeats or hangs on the same item of code. I can run a WB on my own machine a number times no problem, come to run it again and it crashes, I haven't managed to find any clue as to what could be a trigger for this seemingly random behaviour, but I really think it's a Microsoft issue.
This happens now on, I think, all of our macro enabled WB's, I've checked all the permissions (Which haven't changed anyaway), Trust centre settings etc, our IT team manage Win updates. There is definitely nothing wrong with the code, as these are long proven WB's, and it has now affected so many.
I've been aGoogling and I'm finding numerous similar questions raised on the MS Community without yet being able to find a definitive cause or fix, so being as it seems to be an issue affecting Excel specifically, I thought I'd ask here with so many users to see if anyone else is seeing it?
