[AccessD] ADO Command object

Hmmm... my understanding was that you needed the Command object to use
CommandType, so how would using a Connection object to connect be an
advantage with parameters?

Susan H.


> One major one is that the Command object has the parameters collection
that
> is vital to either passing parameters to a Stored Procedure or a
> paramterized Query.
>
> Chris Mackin
> www.denverdb.com
> Denver Database Consulting, LLC
>
>
> -----Original Message-----
> From: accessd-admin at databaseadvisors.com
> [mailto:accessd-admin at databaseadvisors.com]On Behalf Of Susan Harkins
> Sent: Tuesday, March 11, 2003 10:56 AM
> To: AccessD at databaseadvisors.com
> Subject: [AccessD] ADO Command object
>
>
> I see a lot of code that uses the Command object but connects via a
> Connection object, when a Command object can do the same thing. I assume
> this arrangement nets advantages -- can someone name a few?
>
> Susan H.
>
>
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>