Buggy Script of DOOM!

There is one issue with VBscript that I was aware of, but didn't pay it much mind; it is nearly impossible to debug. When I got the script working on my PC and a few others I thought I was home free, oh how wrong I was.

I moved to another PC, confident that I would be able to quickly install the script and move on. I ran a test of the script, only to find it wasn't working. After some quick debugging I found the culprit line of code, which didn't make any sense. If it worked on a number of other PCs, why would this one not work?

Then I remembered some random update that came down a while ago that crippled another macro of mine. It changed the window to cause a cross-scripting error. I still don't know how this is possible because the window doesn't use any frames that I can find, but once I added the site to my list of trusted sites the problem went away.

My natural conclusion was that this was the problem. I added the site to the trusted ones, and even lowered a few cross-scripting rules along with some activeX ones just for good measure, and nothing. I played with the PC for about an hour, and nothing would work, the same line of code still bombed out.

Eventually I decided it was best to see how the settings do tomorrow. I've experienced in the past how IE settings can take a VERY long time to actually take affect. So I'm hoping that tomorrow the PC will work. I have one more security trick left, but otherwise I'm at a loss. I like to blame Microsoft, since it's easier than blaming me.