At the very least, declare your ADODB.Connection object above the sub,
in the Declarations section, and only explicitly set it to Nothing at
the end of your code. That way you'll keep the connection open
throughout.


--JP


On Sep 22, 12:43*pm, WhytheQ wrote:
Has anybody ever written code using the ADO which fires several SQL
strings at SQL server and then copies and pastes each result into a
different worksheet?

I have to execute 15 queries - each takes 2 minutes. So if I can set
them running at the same time things should only take 2 minutes
whereas if I do one after another I'm looking at tying up Excel for 30
minutes !

Or does anybody understand my problem and know of a possible
workaround.

Any help much appreciated,
Jason.