🚀 go-pugleaf

Yuancai

	Thanks for the advice and the site.  I found that the curser
was set to client.  When I set the curser to Server side it speed
things up a lot.  In fact one process that validated and moved over
half a million records that took 11 hours dropped down to 35min with
that one modification.

Mike

On Wed, 24 Jan 2001 14:56:18 -0500, "Yuancai \(Charlie\) Ye"
<yekerui@yahoo.com> wrote:

>Hi, Michael:
>    Did you try using OLEDB raw interfaces to speed up navigating records.
>Here is the excellent site you may be interested in,
>http://www.geocities.com/oledbpro/. The site has many OLEDB examples using
>both Visual C++ and Borland C++ Builder.
>
>Yuancai (Charlie) Ye
>
>"Michael Crapo" <mcrapo@tng-ida.com> wrote in message
>news:3a687d67.14273083@newsgroups.borland.com...
>> Hello.
>>
>> I have test this with Access and SQL Server.  I connect to the
>> database using the TADOConnection. Then run a query using TADOQuery
>> that is selecting one row from a table.
>>
>> The recordcount is about 100,000.  I then loop through the Records
>> using the TADOQuery::Next() function.  The further into the recordset
>> I go, the slower the fields are returned.  I am using defaults for
>> borlands defaults for ADO.  Does anyone know what is wrong, and how to
>> get around this.  It gets as bad as 1 second to return 1 record.....
>>
>> TIA for you help
>> Mike
>
>