I personally think this debate about Command Object versus Recordset Objects is academic and misleading. They each have their own place and some things can only be done with the Command Object and some only with the Recordset object.
If you are using a recordset object you must be dillgent of its default behaviour. For example, the default cachesize parameter is one record. This means that every movenext will result in a round trip across the network (read: slow). Setting the cachesize to a larger figure for a read-only, forward-only recordset can yield a significant performance improvement.
Similarly setting a recordset into batch update mode can out perform single insert/update SQL commands into a command object or connection.execute
If you do not wnat to take the time to consider where and how updates are occuring then the defaults are a good safe setting. If you need speed then then playing with these settings and with the other objects can yeild rich rewards.
Keep Up with TechRepublic