ODBC vs ADO, which is better ?

Dear All,

right now, I'm still rather confused about ODBC and ADO.
Some people said that nowadays, ADO connection have good performance,
compared to the other database connection, while ODBC is said to be
slower that ADO.

But when we use ADO, we must provide a DSN. And in my opinion, DSN is
similar to any ODBC connection.

is there anyone have good explanation about this ?

Good Morning!

They go hand in hand.

You create an ODBC connection to the database, then
assign that connection to the ADOConnection component.

The ADOConnection component serves the same
function as the Database Component: it connects to the
database. Then you use the other ADO components to put
and get data.

Back in the bad old days, ODBC = slow performance.
Nowadays, that is not true.

Caution: make sure you are using the latest MDAC.
Also, if you are using D5 and ADO, get the Delphi ADO
patch. It fixed a problem that MS introduced in the
MDAC.

HTH...Dan'l

--- Alex Oentoro <alexssbygmail.com> wrote:

> Dear All,
>
> right now, I'm still rather confused about ODBC and
> ADO.
> Some people said that nowadays, ADO connection have
> good performance,
> compared to the other database connection, while
>; ODBC is said to be
> slower that ADO.
>
> But when we use ADO, we must provide a DSN. And in
> my opinion, DSN is
> similar to any ODBC connection.
>
> is there anyone have good explanation about this ?
>
>
>
-----------------------------------------------------
> Home page: http://groups.yahoo.com/group/delphi-en/
> To unsubscribe:
> delphi-en-unsubscribeyahoogroups.com
> Yahoo! Groups Links
>;
>
> delphi-en-unsubscribeyahoogroups.com
&gt;
>
>
>
>
>

____________________________________
Every day is a Great day, but
some days are GREATER than others!

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

For me the answer has to be ADO.

I use ADO all the time and never touch ODBC or DSNs (ever). ODBC has
too many bad memories for me and is not required for ADO - or not that
I'm aware of.

Simply set the connection string property and you're in business -
doesn't matter whether it's Access, MSSQL or whatever.

To make connection strings easier to build - create a new text file in
your project folder and rename it anything.UDL Then double click it and
you will get the data link editor - go to the Provider tab and from
there follow the wizard, this allows you to interractively build/test
your connection. Once you've got it working:

In Delph you can use the UDL file directly :
ADOConnection.ConnectionString := 'file
name='&#43;ExtractFilePath(Application.EXEName)+ 'anything.UDL';

This way your users can change their own connection details if the
database/server changes but your code stays the same.

Hope that helps
Dave

GreatDayDan wrote:

>Good Morning!
>
> They go hand in hand.
>;
> You create an ODBC connection to the database, then
>assign that connection to the ADOConnection component.
>
>; The ADOConnection component serves the same
>function as the Database Component: it connects to the
>database. Then you use the other ADO components to put
>and get data.
>;
> Back in the bad old days, ODBC = slow performance.
>Nowadays, that is not true.
>;
> Caution: make sure you are using the latest MDAC.
>;Also, if you are using D5 and ADO, get the Delphi ADO
>patch. It fixed a problem that MS introduced in the
>MDAC.
>
>HTH...Dan'l
>
>--- Alex Oentoro <alexssbygmail.com> wrote:
&gt;
>
>
&gt;>Dear All,
>>
>&gt;right now, I'm still rather confused about ODBC and
>&gt;ADO.
&gt;>Some people said that nowadays, ADO connection have
>>good performance,
>>;compared to the other database connection, while
>;>ODBC is said to be
>&gt;slower that ADO.
>>
>&gt;But when we use ADO, we must provide a DSN. And in
>&gt;my opinion, DSN is
>&gt;similar to any ODBC connection.
>>
>>is there anyone have good explanation about this ?
>>;
>>
>>
>>
>>
>-----------------------------------------------------
>
>
&gt;>Home page: http://groups.yahoo.com/group/delphi-en/
>>To unsubscribe:
>>;delphi-en-unsubscribeyahoogroups.com
>>Yahoo! Groups Links
>;>
>>
>&gt; delphi-en-unsubscribeyahoogroups.com
&gt;>
>;>
>>
>>
>>
>>
&gt;>
>>
>
>;
>____________________________________
> Every day is a Great day, but
>some days are GREATER than others!
&gt;
>__________________________________________________
>Do You Yahoo!?
&gt;Tired of spam? Yahoo! Mail has the best spam protection around
>http://mail.yahoo.com
>
&gt;
>-----------------------------------------------------
>Home page: http://groups.yahoo.com/group/delphi-en/
>To unsubscribe: delphi-en-unsubscribeyahoogroups.com
>Yahoo! Groups Links
>;
>
&gt;
>
>
&gt;
>
&gt;
>

Isn't it true that ODBC is just a collection of functions and
procedures that are used in the old way, without any objects? And
that ADO is based upon a class structure with classes containing
methods to operate on databases?

More info:
http://en.wikipedia.org/wiki/ODBC
http://en.wikipedia.org/wiki/ActiveX_Data_Objects

Thus, ODBC is procedural and ADO is class-based. And ADO wraps around
ODBC but also several other database API's.

Blessed Be(e),
Lisa Westveld.

--- In delphi-enyahoogroups.com, "Alex Oentoro&quot; <alexssby...> wrote:
&gt;
> Dear All,
>
> right now, I'm still rather confused about ODBC and ADO.
> Some people said that nowadays, ADO connection have good performance,
> compared to the other database connection, while ODBC is said to be
> slower that ADO.
>
> But when we use ADO, we must provide a DSN. And in my opinion, DSN is
> similar to any ODBC connection.
>
> is there anyone have good explanation about this ?
>

Alex Oentoro wrote:
&gt; Dear All,
>
> right now, I'm still rather confused about ODBC and ADO.
> Some people said that nowadays, ADO connection have good performance,
> compared to the other database connection, while ODBC is said to be
> slower that ADO.
>
> But when we use ADO, we must provide a DSN. And in my opinion, DSN is
> similar to any ODBC connection.
>
> is there anyone have good explanation about this ?

ODBC offers the maximum portability for applications. That's assuming
you want to eventually port to other OSes (e.g. Linux or Mac). ADO ties
you to Windows. Supposedly ADO is easier to use, but I've got ODBC
wrappers that hide the ugly side of ODBC quite nicely so the difference
(from my perspective) is one of portability, not performance or ease-of-use.

Just a thought.

--
Thomas Hruska
CubicleSoft President
Ph: 517-803-4197

Safe C++ Design Principles (First Edition)
Learn how to write memory leak-free, secure,
portable, and user-friendly software.

Learn more and view a sample chapter:
http://www.CubicleSoft.com/SafeCPPDesign/