× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: MS ADO with CA Express ADO vs. CA Express ODBC?
  • From: "Luther Ananda Miller" <luther.miller@xxxxxxxxxx>
  • Date: Wed, 13 Oct 1999 18:04:33 +0200

I am looking to use MS ADO in VB and given the choice of connecting to CA
Express ODBC drivers or ADO drivers, I would prefer using the ADO drivers.
However it looks like there are a couple of limitations:

1) It appears we cannot pass the userid/password in on connect, but the
client access prompt must be used instead (unlike when using the ODBC
drivers). Is there a way to pass these instead?

2) Can't find a way to set the default library. If we use ODBC we can set up
DSNs and specify the default library.... isn't there a similar mechanism
with Client Access's ADO drivers? DefaultDatabase property on the Connection
object seems to not be supported by the drivers.

3) I assume I am going to miss out on some potential performance benefits if
we use MS ADO objects to connect via CA ODBC DSNs instead of CA ADO -- what
kinds of performance differences are there between these two methods?

Luther

luther.miller @ hypere.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.