I am seeing some strange behavior from a specific computer, and was curious if anyone else has ever seen this. I am confident the issue does not lie within the VBA code itself, as it runs fine most of the time on this computer, and always runs without error on my second computer running the same OS / MS Excel.
The behavior is that if I force stop a macro (CTRL + Break) OR sometimes if a macro legitamately bugs out on this computer, its like something gets "stuck" in the memory and subsequently after that all macros throw an error on random lines of code until I reboot the computer.
That is to say, established macros that are not in development throw errors. The strangest part is I can continue through the code hitting F8, and successfully get to the end of the macro with it completing everything that it was supposed to do, only it stops every couple of seconds and tosses me into VBE with a random line highlighted..
My IT Department has re-imaged my computer several times since this behavior started, but it has persisted...
Was curious if anyone else has ever witnessed this that could maybe shed some light onto the most likely culprits... Its seems if there was a hardware issue (like a memory leak) that I would experience other symptons outside of Excel VBA, however that is not the case...
Thoughts? Suggestions? Ideas?
The behavior is that if I force stop a macro (CTRL + Break) OR sometimes if a macro legitamately bugs out on this computer, its like something gets "stuck" in the memory and subsequently after that all macros throw an error on random lines of code until I reboot the computer.
That is to say, established macros that are not in development throw errors. The strangest part is I can continue through the code hitting F8, and successfully get to the end of the macro with it completing everything that it was supposed to do, only it stops every couple of seconds and tosses me into VBE with a random line highlighted..
My IT Department has re-imaged my computer several times since this behavior started, but it has persisted...
Was curious if anyone else has ever witnessed this that could maybe shed some light onto the most likely culprits... Its seems if there was a hardware issue (like a memory leak) that I would experience other symptons outside of Excel VBA, however that is not the case...
Thoughts? Suggestions? Ideas?