Nick and hAlim,

Your emails both confirm my that it must be a qualification or
object-release issue. I will check the code once more (a little later today)
once more and if I cant see anything I will post the code. Otherwise I'll
notify you what I found.

Thanks,

" wrote:

Hi Ali,

Better you post your first running code, and let me guess that
possibility is by :
Dim Wb as Excel.Application

or something like that, that not bring the object visible is true but
visible is false .

try to post your code ... that error occured

Thanks,

hAlim

Arif Ali menuliskan:

In the past I learned that using fully qualfiied workbook, sheet and range
names eliminated similar problems. But even with fully qualified references,
this problem remains. I am urgently trying to release the latest version of
this tool to my coworkers, but I am stumped as to the cause of this problem.

Any ideas?