🚀 go-pugleaf

Vassiliev, thanks for your answer.

However, that was not my question. I think I didn't explain it correctly.
I'm trying to find out how I can read the records that the SQL Server has
already returned.
That's why I'm using eoAsyncFetch. I want to start displaying records to the
user even when
the query hasn't finished yet.

Thanks



"Viatcheslav V. Vassiliev" <support@oledbdirect.com> wrote in message
news:41073cac@newsgroups.borland.com...
> If you do not display your query in UI - use server-side cursor, it will
not
> fetch all rows into memory.
>
> //------------------------------------------
> 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)
>
> "Star" <---> �������/�������� � �������� ���������:
> news:4106de81$1@newsgroups.borland.com...
> > Hi,
> >
> > I have very big table (about 50 million records). I usually make some
> > queries on this table, and it can take
> > several minutes to run. Is there anyway to start getting records as soon
> as
> > there is one available?
> >
> > I thought I could use something like this:
> >
> > ADODataSet1->CommandText = "SELECT Code From Subs_Subjects";
> >
> > ADODataSet1->ExecuteOptions = ADODataSet1->ExecuteOptions <<
eoAsyncFetch;
> > ADODataSet1->Open();
> >
> > Is that the way to do it? Should I get an event for every new record
> > returned? In that case, what event should I look at?
> >
> > Thanks
> >
> >
>
>