Re: ADO vs dbExpress

Guillem wrote:

as an addition to what Brian says, dbExpress uses unidirectional
cursors, a limitation that ADO has not.

Only if you do not use a ClientDataSet. If you do, then you get the
same behavior that you get with ADO and a client side cursor. However,
I agree that ADO is the best choice for SQL Server.

--
Bill Todd (TeamB)
.

Relevant Pages

  • Re: ADO vs dbExpress
    ... cursors, a limitation that ADO has not. ... dbExpress is designed to be used with clientdatasets which give ...
    (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: Questions about ADO
    ... Thanks for the pointers and the website. ... > I also believe Server / Client side cursors will affect RecordCount. ... > Better to refer to the programmers reference and Provider documentation. ... > with ADO programming. ...
    (microsoft.public.excel.programming)
  • Re: I get this message
    ... MS SQL, ADO components from D7. ... The clientdataset delete works but the applyupdates fails. ... Russ ...
    (borland.public.delphi.database.ado)
  • Re: Developer Use of Visual Basic Plummets
    ... The ClientDataset, as I understand it, is an in-memory dataset and it's not ... other server connected processes for mullti-tier apps. ... (their ADO has a thin ADODataSet that looks a lot like the ClientDataset). ...
    (microsoft.public.vb.general.discussion)