[AccessD] ADO Command object

Francisco H Tapia my.lists at verizon.net
Wed Mar 12 10:07:00 CST 2003


Susan,
   Check out YOURS and Martin's book (Sql: From Access to SQL Server) pages
643 (1st Note), and pages 668-670 for an explanation of why you would use a
connection object.


-Francisco
http://rcm.netfirms.com

On Tuesday, March 11, 2003 2:01 PM [GMT-8],
Susan Harkins <harkins at iglou.com> wrote:

:: 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).
:
: =============I'm not sure what this means. I'm not using
: CurrentProject.Connection, but a connection string that's connecting
: to whatever I want. I don't seem to have lost a thing by doing so --
: I still don't see the advantage of using the Connection object
: instead of a connection string.
:
: I'm not arguing -- I just don't understand. The light's not going on.
: :)
:
: Susan H.
:
: _______________________________________________
: AccessD mailing list
: AccessD at databaseadvisors.com
: http://databaseadvisors.com/mailman/listinfo/accessd
: Website: http://www.databaseadvisors.com





More information about the AccessD mailing list