Throwback Thursday: August 27, 2026
In today's edition of Throwback Thursday, we revisit some advanced tips for debugging "Automation" errors with those crazy numbers, like -2,147,024,891.
With over a million words scattered across more than 1,800 articles on this blog, you've probably missed a few things here.
That’s why each week in "Throwback Thursday," we’ll revisit some standout posts. Expect a blend of my personal favorites, insightful articles from other great minds, and a touch of coding humor to keep things light.
Highlights from NoLongerSet.com
Debugging Automation Errors
Come join me on a journey debugging hard-to-reproduce “Automation error” bugs.
Mike Wolfe
Breaking Down Windows Error Codes
Did you know there is a method to the madness behind those crazy-looking VBA error numbers like 0x80070005 or its decimal equivalent -2,147,024,891?
Mike Wolfe
3 Benefits of Documenting Your Debugging Process
It may sound counterintuitive, but taking the time to document your debugging process will save you time--both now and in the future.
Mike Wolfe
Wisdom from Around the Web
Structure of COM Error Codes - Win32 apps
Structure of COM Error Codes
GrantMeStrength
[MS-ERREF]: Win32 Error Codes
All Win32 error codes MUST be in the range 0x0000 to 0xFFFF, although Win32 error codes can be used both in 16-bit fields
Process Monitor - Sysinternals
Monitor file system, Registry, process, thread and DLL activity in real-time.
markruss
Developer Humor
Code Quality 2
Cover image generated by Ideogram
