Home |
Search |
Today's Posts |
#12
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I'm actually implenting a VBA script which performs a search
through several hundred Excel workbooks, and I want this search to run as quickly as possible. Opening and closing a couple hundred macro enabled workbooks seems kinda time consumining, so I figured why not use ADO to run the search more quickly. Gary made the following comment in a past post to me: - "The point I was trying to make is that using the methods demonstrated in Rob's examples doesn't require opening anything. I don't understand why you'd want to open all those files when it's not necessary AND it will slow down your procedure to a crawl and then possibly an out of memory crash." He was basically saying that I can use ADO to avoid opening "all those files when it's not necessary". I just figured I would experiment with Gary's suggestion and see if it runs faster than the alternative. 8) "norie" wrote in message ... I agree with Garry if it's one cell what's the point in GetRows, but I would take it a wee bit further? Why use ADO to get one value from a workbook?? |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
writing ADODB recordset to excel sheet | Excel Programming | |||
VBA excel - problem with having clause in sql with adodb.connection/recordset | Excel Programming | |||
0 with ADODB Recordset | Excel Programming | |||
adodb.recordset with excel | Excel Programming | |||
ADODB Recordset | Excel Programming |