When I get to Chapters 6 and 7, which are all about Recordsets, I discuss lots of different ways to execute queries—many of which don’t require use of the Command object to construct. The one important case where the Command object is required is when you have to capture parameters returned from stored procedures. ADO is very smart when it comes to handling stored procedures. If you aren’t returning OUTPUT parameters, and if you don’t care about the stored procedure return value, you don’t have to construct a Command object—so don’t. On the other hand, I encourage you to use OUTPUT parameters instead of Recordsets. A resultset with a dozen dozen OUTPUT parameters is still faster to manage than a single-row Recordset. But then, almost any approach is faster than constructing a Recordset.


Round Trip Parameter Object Data Provider Visual Basic Execution Plan 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Copyright information

© Apress 2002

Authors and Affiliations

  • William R. Vaughn

There are no affiliations available

Personalised recommendations