Yup. As long as the OP understands that there may not be a causal
relationship between something that looks faster and the solution to the
root of the problem. From the way the latter half of the thread was
progressing, it seemed that the underlying problems were starting to get
ignored. I have seen it time and again where developers get involved in
similar predicaments, try this..try that..try the other thing...to the Nth
degree....then arrive at a final solution where they categorically embrace
or reject some Excel objects or coding styles based on false assumptions.
Just trying to keep that in check...



--
Regards,
Tim Zych
http://www.higherdata.com


"Patrick Molloy" wrote in message
...
if its not possible to isolate the issue, and from the length of this
thread that's a possibility, then i see no reason not to offer a
reasonable alternative. Nor is it "my" system that's the issue ...

"Tim Zych" <tzych@nospam at earthlink dot net wrote in message
...
Did you try my last idea? I think you still need to isolate what the
problem really is. Most of the code improvements are valid. The fact they
don't work quickly on your system is what should be explored more.

--
Regards,
Tim Zych
http://www.higherdata.com
Workbook Compare - Excel data comparison utility
<<< SNIP