Module level variable going out of scope

[Quehay]

I've got an Excel object variable declared in the page-level declarations. I initialize it in a sub and then refer to the variable in other subs. It worked but has stopped working (getting "object required" errors when trying to refer to it).

This should not be happening, and it appears that the scripting host is closing the variable prematurely. Has anyone else experienced this?

Thanks!


Jeff Roberts
Insight Data Consulting
Access and SQL Server Development

http://www.InsightDataConsulting.com

 

[tsuji]

Hello Quehay,

Maybe you need to reinstall the wsh over itself. (You know, it takes <10sec and seamless.) Make sure v5.6 latest.

regards - tsuji

 

[Quehay]

tsuji,

Thanks--I wondered if maybe the dll was fried or something. I found an earlier version of the same script that ran correctly (I printed copies and there were NO DIFFERENCES in the problems areas). So I copied new subs/lines into the old script, and it ran. This was the most mysterious programming bug I've encountered.

Jeff


Jeff Roberts
Insight Data Consulting
Access and SQL Server Development

http://www.InsightDataConsulting.com