Re: ADOQuery or ADOTable?

Larry Killen wrote:

>
> As per Delphi Help. a TADOQuery must be used for DML.
> TADODataSet is not capable of issuing Data Manipulation Language
> (DML) SQL statements that do not return result sets (like DELETE,
> INSERT, and UPDATE). For this use a component like TADOCommand or
> TADOQuery. Larry Killen
>

ummm, true. I forgot that one :) Well, personally i always use a
combination of TADODataset + TADOCommand and not TADOQuery, but that
could be seen as personal POV. Either case, TADOTable should be avoided

--
Best regards :)

Guillem Vicens
Dep. Informática Green Service S.A.
www.clubgreenoasis.com
--
in order to contact me remove the -nospam
.

Relevant Pages

  • Re: ADOQuery or ADOTable?
    ... TADOQuery is ok for querys, but as TADODataset has all the ... > features, ... As per Delphi Help. ... TADODataSet is not capable of issuing Data Manipulation Language SQL ...
    (borland.public.delphi.database.ado)
  • Re: slow refresh of mysql datasets via ADO
    ... the nasty habit to try to load the whole table data. ... TADODataset instead. ... I already got rid of the table. ...
    (borland.public.delphi.database.ado)
  • Re: Changing DB with TADOConnection
    ... >to the new DB and can even oepn up a TADOQuery and manipulate it. ... >However, when I then go to open a TADODataset, I get either a "stack ...
    (borland.public.delphi.database.ado)
  • Re: Changing DB with TADOConnection
    ... >ok I switch the TadoDataset to a TadoQuery and I am testing with D5 ... >No problem with previously posted code ... Hmmm, I wonder if it has to do with multiple ado datasets. ...
    (borland.public.delphi.database.ado)