Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
ADO Recordset vs Command
- Thread starter venom3249
- Start date
stoolpigeon
Programmer
It depends on what you are doing.
If you do not need anything back from the database- then the overhead of a recordset is not necessary.
Usually you can do most needed operations without a command object either. I have found that in 90% of my database apps I use just connections and recordsets. I only use recordsets when I need information returned from the database. I do not use recordsets for updates or inserts.
It is also very helpful to use forward only/read only recordsets whenever possible.
If you do not need anything back from the database- then the overhead of a recordset is not necessary.
Usually you can do most needed operations without a command object either. I have found that in 90% of my database apps I use just connections and recordsets. I only use recordsets when I need information returned from the database. I do not use recordsets for updates or inserts.
It is also very helpful to use forward only/read only recordsets whenever possible.
- Status
