A
Amanda V
Hello,
I am making a VB6 application to automate an MS Access database.
One can only use the .RecordCount property with certain cursortypes,
but those cursor types do not let me use the rst.MoveFirst property as
well.
Would it be very costly in terms of resources to just re-open the
recordset again instead of using rst.MoveFirst to return to the
beginning of the recordset? Or is there a combination of rst properties
that will allow me to know how many records were returned in the
recordset AND still be able to easily navigate forward and backwards
through my recordset?
I've already tried using adOpenDynamic and it returns -1
Thanks!
Amanda
P.s. Also looking for an article or link with tips on a resource
efficient application, that would be great. Tips like, "instead of
using a connection string, pass a connection object when opening
multiple recordsets"... etc... My overall goal is to get fast
performance by not eating up resources with costly code (but whose
isn't?
I am making a VB6 application to automate an MS Access database.
One can only use the .RecordCount property with certain cursortypes,
but those cursor types do not let me use the rst.MoveFirst property as
well.
Would it be very costly in terms of resources to just re-open the
recordset again instead of using rst.MoveFirst to return to the
beginning of the recordset? Or is there a combination of rst properties
that will allow me to know how many records were returned in the
recordset AND still be able to easily navigate forward and backwards
through my recordset?
I've already tried using adOpenDynamic and it returns -1
Thanks!
Amanda
P.s. Also looking for an article or link with tips on a resource
efficient application, that would be great. Tips like, "instead of
using a connection string, pass a connection object when opening
multiple recordsets"... etc... My overall goal is to get fast
performance by not eating up resources with costly code (but whose
isn't?
