Re: Migrating to OLEDB

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Yuancai \(Charlie\) Ye (someone_at_yahoo.com)
Date: 04/23/04 

Date: Fri, 23 Apr 2004 13:19:10 -0400

Hi, David:
     I did a lot with OLEDB. See the library OleDBPro I wrote at
www.udaparts.com.

    Basically, OLEDB is better than ODBC and others in many aspects.
    1. OLEDB is a complete soluntion to all of your data sources.
    2. OLEDB is highly extensible, but ODBC is not. Actually there is no
other standard database interface more extensible than OLEDB.
    3. MS provides more important data services with OLEDB, but MS
doesn't with ODBC.
    4. OLEDB has the same level of performance with ODBC. Specifically,
SQL Server and Oracle providers are faster than their ODBC drivers now.
Actually there is no other standard database interface faster than OLEDB in
general. ADO.net can match OLEDB in retrieving records only.
    5. An OLEDB provider provides more features than its corresponding
ODBC. Actually there is no other standard database interface providing more
features than OLEDB. ADO.NET can not match OLEDB in this aspect.
    6. OLEDB provides better multithreading and notification support than
ODBC. ADO.NET can not match OLEDB in this aspect.
    7. OLEDB is more flexible than ODBC. Actually there is no other
standard database interface more flexible than OLEDB.
    8. MS doesn't advance ODBC any more, but still advance OLEDB.

    OLEDB has one famous flaw, complexity (don't count ADO). Actually, there
is no other database interface as complicate as OLEDB.

Yuancai (Charlie) Ye
RDB, a tool for fast and securely accessing remote databases with dial-up,
cable, DSL and wireless modems anywhere

Fast and securely accessing all of remote data sources anywhere with
SocketPro using batch/queue, non-blocking and parallel computation

See 30 well-tested and real OLEDB examples
www.udaparts.com

"David Pineda" <anonymous@discussions.microsoft.com> wrote in message
news:57BCA11E-158D-4CEA-BD04-FEC8E78E6C29@microsoft.com...
> I need some advice; I developed an VC++6.0 application that use ODBC API.
Now I need to migrate this to OLEDB in a way that works for VC++6.0 and
VC++.NET.
>
> What recommendations do you have? Someone have some development like this?
>
>
> I really appreciate very much any help.
>
> David

Relevant Pages

  • Re: Migrating to OLEDB
    ... Certainly OLE DB is extremely flexible and I certainly understand that the ... in making a decision to use OLE DB over ODBC for a "typical" application. ... I am presently grappling with problems with OLEDB in our own application (an ... request a Forward-Only, Static, Keyset Driven, or Dynamic cursor type ...
    (microsoft.public.data.odbc)
  • Re: Migrating to OLEDB
    ... Certainly OLE DB is extremely flexible and I certainly understand that the ... in making a decision to use OLE DB over ODBC for a "typical" application. ... I am presently grappling with problems with OLEDB in our own application (an ... request a Forward-Only, Static, Keyset Driven, or Dynamic cursor type ...
    (microsoft.public.data.oledb)
  • Re: VFP Updates?
    ... Try talking ODBC or OleDb and they say HU. ... make up my apps so that what ever they want to run has to be from a command ... kind of connection and assign it the right to do exactly what you want. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Migrating to OLEDB
    ... See 30 well-tested and real OLEDB examples ... In our tests the ODBC ... to have LOTS of features and to support ... >> YCY> Specifically, SQL Server and Oracle providers are faster than ...
    (microsoft.public.data.oledb)
  • Re: Migrating to OLEDB
    ... See 30 well-tested and real OLEDB examples ... In our tests the ODBC ... to have LOTS of features and to support ... >> YCY> Specifically, SQL Server and Oracle providers are faster than ...
    (microsoft.public.data.odbc)