.... but note that ADO is many times faster than using automation.

"Tom Ogilvy" wrote in message ...
I don't think you need to have Excel installed to use ADO.

Obviously managing Excel through automation offers much, much more
capability.

--
Regards,
Tom Ogilvy

Eric wrote in message
...
Ok, I added IMEX=1 and it worked. No, we won't be writing to Excel so
that
should be fine. The other way should work too once I figure out if
there's
a way to tell it the last row and column that contains data, or if that
will
work with a while loop that gets next instead of the for-next.
Is there an advantage to using ADO or the Excel.Application,
Excel.Workbook...?


"Tom Ogilvy" wrote in message
...
http://support.microsoft.com/default...b;en-us;257819
HOWTO: Use ADO with Excel Data from Visual Basic or VBA

It discusses this down around the middle of the article. talks about an
extended property of IMEX=1

To work around this problem for read-only data, enable Import Mode by
using
the setting "IMEX=1" in the Extended Properties section of the
connection
string. This enforces the ImportMixedTypes=Text registry setting.
However,
note that updates may give unexpected results in this mode. For
additional
information about this setting, click the article number below to view
the
article in the Microsoft Knowledge Base:
194124 PRB: Excel Values Returned as NULL Using DAO OpenRecordset



--

Regards,

Tom Ogilvy