[AccessD] ADO Command object

Since I'm working strictly in an ADP, I don't bother to use the Connection
object at all.  I can see using it if I needed to connect to something other
than the CurrentProject.Connection (or anything you can get to through it).

In my error handler code, I cycle through the
CurrentProject.Connection.Errors collection for information relating to the
failure of the Command object.

Doris Manning
Database Administrator
Hargrove Inc.
www.hargroveinc.com


-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Tuesday, March 11, 2003 03:01 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] ADO Command object


How do you handle errors in a Command object then? 

Susan H. 


> Well, the Connection object has properties that make it easier to see 
> and set the various pieces of the connection string instead of 
> creating one huge string that you then may have to debug when it 
> doesn't work. You can't get there through the Command object.  It also 
> has the errors collection you'll need for any error trapping.  I 
> personally find it easier to work with cnn.Errors than having to go 
> through the command object first.
> 
> Charlotte Foust