Re: ADO vs dbExpress


as an addition to what Brian says, dbExpress uses unidirectional
cursors, a limitation that ADO has not.
That really falls under the ease of use issue which wasn't explicitly part of
the question. dbExpress is designed to be used with clientdatasets which give
you the same functionality but with a bit more programming. A better ease of
use issue is that ADO handles updating joins with out having to write additional
SQL
--
Brian Bushay (TeamB)
Bbushay@xxxxxxxxx
.

Relevant Pages

  • Re: ADO vs dbExpress
    ... cursors, a limitation that ADO has not. ... Only if you do not use a ClientDataSet. ... same behavior that you get with ADO and a client side cursor. ...
    (borland.public.delphi.database.ado)
  • Re: DAO to ADO Recordset Options
    ... DAO was really fast when dealing with Access data (faster than ADO) but was ... Recordset. ... For client-sided cursors, there is only Static cursor type regardless as ... determines how often data is fetched from the server. ...
    (microsoft.public.data.ado)
  • Re: dbExpress als Alternative für FIBPlus?
    ... und Oracle 9i mit dbExpress gearbeitet und war durchaus angetan. ... habe zwar auch gute Erfahrungen mit ADO und ADO.Net für den Zugriff auf ... OLEDB-Treibern für den Zugriff auf FireBird mittels ADO gemacht hat, ... > das ein Vorteil?), die Dokumentation scheint gut zu sein, es gibt ...
    (de.comp.lang.delphi.datenbanken)
  • Re: Delphi books of intrest?
    ... I'll cover the Borland Database Engine, dbGo for ADO, dbExpress ... and the stand-alone TClientDataSet. ... Delphi, although ADO needs Delphi 5 or higher, dbExpress needs Delphi ...
    (borland.public.delphi.non-technical)
  • Re: ADO vs dbExpress
    ... dbExpress is the better choice for DB connectivity? ... We are currently using SQL 2005 and ADO seems like a logical choice, ...
    (borland.public.delphi.database.ado)