Count Number Of Records Returned by ADODB

Hi-

Why not use the excel rows.count?
or if you really want via sql then

Please Login or Register  to view this content.

Regards,
Event

Did you try the suggestions on your other thread? You really shouldn't be using ADO like this and certainly not for a client. You shouldn't hand over buggy, memory leaking code.

@Kyle123
Thank you for your suggestion again. In the final deliverable I am querying from another workbook only.

@Kyle123 & even21
I think there is some property like RecordCount with RecordSet. Can you guide me how to use it?

Like this, but as you're still learning to use ADO, you'd be better with early binding so that you have the global constants and intellisense

Please Login or Register  to view this content.

@JosheP & @Kyle123:

Thank you for your answers. As per http://support.microsoft.com/kb/319998, Microsoft suggests using SELECT INTO to avoid memory leak.
So does it apply to INSERT INTO also??

There is no issue with either as long as the workbook is closed. You shouldn't really be querying open workbooks.

SELECT INTO only bypasses the memory issue in the sense that you are supposed to use it to export your source data to a new closed workbook and then query that, thereby avoiding the issue caused by repeated querying of an open workbook. Using it to create a new sheet in the open workbook would not help you. In that sense INSERT INTO would help only if you inserted the data into an existing closed workbook.

Ok thank you experts!