Problems with ADO connection to same workbook?
 

I have a workbook in which I have an ADO connection to itself, so that I can
use SQL to get arrays of data I want for processing in VBA. But I suspect it
is responsible for intermittent instabilities - typically an ADO related
error message about 'Network connection may have been lost'. Does anyone
recognise this problem? Is this self references connection object just
inherently flakey? Any "dos" and "don'ts"?

Problems with ADO connection to same workbook?
 

http://support.microsoft.com/default...;319998&Produc
BUG: Memory leak occurs when you query an open Excel worksheet by using
ActiveX Data Objects (ADO)

Most recommend doing a

thisWorkbook.SaveCopyAs "some name"
then ADO to that closed copy.

Delete when done using it.

--
Regards,
Tom Ogilvy


"Tim Lund" wrote:

I have a workbook in which I have an ADO connection to itself, so that I can
use SQL to get arrays of data I want for processing in VBA. But I suspect it
is responsible for intermittent instabilities - typically an ADO related
error message about 'Network connection may have been lost'. Does anyone
recognise this problem? Is this self references connection object just
inherently flakey? Any "dos" and "don'ts"?