🚀 go-pugleaf

Yes, ADO is native for MS Access. But you may try ADO without ADO Express
(dbGo), DAO or even OLEDB or ODBC - this way you will have no TDataSet
descendant but you should have some speed improvement.

By default, ADO Express uses client-side cursor - it fetches all rows into
memory cache, so 1/20 sec. for one select is normal.

//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)

"C�sar" <kaesar2@lycos.es> �������/�������� � �������� ���������:
news:c28n0e$1qcd64$1@ID-201928.news.uni-berlin.de...
>
>     I�m using an ms access local database. The components used are
> TAdoDataSet connected with a TADOConnection.
>     The trouble is that, in spite of the structure of the database, I have
> to use 3 TAdoDataSet opened at the same time. i�m not sure if this can be
a
> trouble.
>
> > 1/20 sec. for one select usually is normal. Of course, you can speed up
> your
> > application if you will use direct API for your DBMS.
> >
>     1/20 sec. is the time my application takes for each sellect more or
> less, so maybe it may be normal the time spent. I think I�m using the
> correct API for the access database, aren�t i?
>
>
>
>