Very true - thanks Harald.

I also believe Server / Client side cursors will affect RecordCount.
Better to refer to the programmers reference and Provider documentation.
There is also a newsgroup devoted to ADO: microsoft.public.data.ado

To be honest, it's difficult remembering this stuff - I hardly ever deal
with ADO programming.
When I first started using ADO, I figured out what worked, wrote a wrapper
library and haven't touched it in years.

--
Rob van Gelder - http://www.vangelder.co.nz/excel


"Harald Staff" wrote in message
...
Hi Hash

Adding toRob: Note that recordcound won't work with cursor "ForwardOnly",
and that ForwardOnly is a lot faster than other cursors on certain
systems.

HTH. Best wishes Harald

skrev i melding news:asYGd.18123$B95.5622@lakeread02...
All -

Working the issue of a large data import, Google led me to ADO. I have
the basic routine working, copyied from a European website.

Right now I determine the size of the import afterwards via xlend etc.
Is there a property I can access before the import (rs.recordcount or
somesuch) that will tell me what the number of records is beforehand so
I can size the copied data? Easy enough for me to do except when I want
all of them. Second question--same for number of fields.

Right now, I count field.names while field(i).name < vbnullstring.
That gives an error, for which I continue on, and capture my counter. A
method that grates. What are the values of "empty" field.names? NULL
doesn't work either.


Thanks in advance.

...best, Hash