Devart Forums

I seem to have a problem with the odac component taking 100% of the cpu while fetching results, even though it only gets about 10 rows/min due to complex query.

So, I have code something like this which just gets all results (and not just the first 25).
Query.First;
Query.MoveBy(Query.RecordCount-1); // step to the last fetched row i think?
While not Query.Eof do
begin
Query.Next;
Label1.Caption := 'Fetching row ' + IntToStr(Query.RecNo);
Application.ProcessMessages;
end;

If I step through this Query.Next is instant 24 times, but the 25th when it needs to get more result it just hangs for a few minutes (while oracle tries to get the results i suppose) and cpu goes to 100% and the application seems to hang (not so nice).

Is this a known problem? Is it fixed in a later version? I made a quick attempt to find where it is but no luck...

We could not reproduce the problem. Please send to odac*crlab*com a complete small sample that demonstrates the problem, including script to create server objects.

Very odd, I started a new project, filled a table with alot of data and a query with filter which fetched 50 or so rows in a couple of minutes. But then it behaved as it should and took no cpu power when waiting for results. Oh well, guess I have to look around if I can find something special in my other application that can cause this...