filled2bursting
New Member
- Joined
- Mar 1, 2012
- Messages
- 6
I have a curious error that appeared in several places at once.
Automation Error - Catastrophic Failure
This all of a sudden started to appear when opening a workbook I had been developing.
In practice I have saved this in a series of versions before advancing stage to stage. As I couldn't figure out the issue I thought to cut my losses and rework from the last stage. Only the issue appeared there again, and on and on stage after stage back nearly a month.
This leads me to suspect there was some configuration change in my system that triggered this. I prefer that to the idea of some latent stealthy bug that could pounce and destroy all your work at any time irrespective of versioning.
When I try to identify the issue in VBA, I am able to find the module its highlighting as the issue.
This is a UDF I've used for years without issue in dozens of other contexts, that I consider to be quite stable.
If I comment this out, the error goes away only to come back on another UDF.
As a note, it appears to just be yell(ow)ing at the first UDF it comes to. If I comment out all of VBA then its good, but when I try to add something back it begins again.
Also with each reset it seems to be copying all the virtual worksheets in the project making it virtually twice as large. When you return out of VBA view though all is normal. (The file size doesn't seem to be increasing).
MSDN talks of "objects". I am not sure what I have in this workbook that would qualify:
In the Book: Moderate sized tables, several pivot tables with slicers, camera tool pictures, and a pair of rectangle shapes with macros assigned.
In VBA: No classes, workbook, sheet, or range objects
Anyone have any ideas on how to short-circuit the game of whack-a-mole?
Otherwise any ideas on how to check for the bug in a rebuild before its too late?
Automation Error - Catastrophic Failure
This all of a sudden started to appear when opening a workbook I had been developing.
In practice I have saved this in a series of versions before advancing stage to stage. As I couldn't figure out the issue I thought to cut my losses and rework from the last stage. Only the issue appeared there again, and on and on stage after stage back nearly a month.
This leads me to suspect there was some configuration change in my system that triggered this. I prefer that to the idea of some latent stealthy bug that could pounce and destroy all your work at any time irrespective of versioning.
When I try to identify the issue in VBA, I am able to find the module its highlighting as the issue.
This is a UDF I've used for years without issue in dozens of other contexts, that I consider to be quite stable.
If I comment this out, the error goes away only to come back on another UDF.
As a note, it appears to just be yell(ow)ing at the first UDF it comes to. If I comment out all of VBA then its good, but when I try to add something back it begins again.
Also with each reset it seems to be copying all the virtual worksheets in the project making it virtually twice as large. When you return out of VBA view though all is normal. (The file size doesn't seem to be increasing).
MSDN talks of "objects". I am not sure what I have in this workbook that would qualify:
In the Book: Moderate sized tables, several pivot tables with slicers, camera tool pictures, and a pair of rectangle shapes with macros assigned.
In VBA: No classes, workbook, sheet, or range objects
Anyone have any ideas on how to short-circuit the game of whack-a-mole?
Otherwise any ideas on how to check for the bug in a rebuild before its too late?
