I agree with Yehuda's obervation.  Depending upon how many and what
type of controls you have, the form loading of the form will slow
down at varing degrees.  After this initial load, the form
seems to run fairly quickly though.

Using your own dll, will be quicker to load, but depending on how
many controls and what types of controls you have, the loading
of the data may be slower.

There is one other consideration though.  As Yehuda also mentioned,
using the ADODC means that you have to bind directly to the
database.  This highly affects the scalability of the application.
By default, the ADODC will keep an open connection to the server
as well as hold resources on the server to handle the recordset
that you happen to have open at any time.  

All this means that during the life of your ADODC you will be 
taking up resources on your data server.  If your application 
will only have 10 people on it, then you will probably be ok.
But if you are writing an application for 100+ users, you will 
experience a large overall performance decrease, not only in your
application, but also any other application that may have
data on the same server. Using a .dll containing the ADODB 
libraries, you will have a lot more coding to do, but you 
have tighter control over how long connections and recordsets exist.

Don't get me wrong though, a programmer can easily just
code a .dll that will have the same performance as the ADODC.
I'm just saying that the programmer can use the higher degree of
control to create a smarter data class.

Cardyin

--------------------------------------
Cardyin Kim
C/S & Web Development Analyst
Information Services
San Antonio Community Hospital
ckim@s...     (xxx)xxx-xxxx     
--------------------------------------

-----Original Message-----
From: Yehuda Rosenblum [mailto:Yehuda@I...]
Sent: Friday, July 20, 2001 6:18 AM
To: professional vb
Subject: [pro_vb] RE: ADODC vs COM


Actually, I have found that using ADODC slows the form load down as it
has to bind the form at the beginning.  Has anyone else noticed this?
The other problem I have with ADODC is it meansa you have to bind the
project directly to the database.  Usually, I prefer to build a logic
layer consisting of a DLL in between the form and the Database.  It is
unfortunate that the new datagrids do not supoort this idea (at least I
can't find a way to use them unbound).