Please kill me
I'm trying to debug an SPSS Visual Basic / ActiveX script right now after it randomly stopped working. It worked perfectly fine for weeks, but yesterday it just stopped for absolutely no reason. Not a character in the source code changed. The thing was marked Read-only; it's not POSSIBLE it changed. So how can it work one minute and stop working the next?
This is very close to what I imagine Hell is like.
"Unknown internal error". You can't get much better than that. Oh wait, I'm sorry, you can. Utilizing state-of-the-art VB debugging techniques, I am able to expand upon that:
**ERROR** ((&H800405e8) Unknown internal error.)
Ah, the old &H800405e8. I should've known! Now I know immediately how to solve this issue. My solution does involve launching my computer in a somewhat ballistic manner off the top of this building, but it couldn't hurt.
SPSS 13 is such a shoddy product, the company that made it should be sued.
4 Comments
Upgrade to SPSS 16.
The company that made SPSS 13 is SPSS Inc. They have a support line.
&H800405e8 really does tell you how to solve the problem (search it in Google) and the solution does NOT involve throwing your computer off a building. Harming the physical machine never fixes a software error. This is a common misconception, so I can understand why you might think this.
Ok I'll stop messing with ya. You need to update your license. Expired
Yes, you would have found your license was expired had you run a Google search. If you instead threw your computer off a building, believe it or not: you would still have an expired license.
Speak your Mind
Preview