🚀 go-pugleaf

Thanks: Yes I found that out that this is the only choice that allows 
indexes and seeks. The application was first developed using the BDE 
with Access 97.
I think I have found that the slow responce is due to many lookup and 
calculated fields.

John
"Viatcheslav V. Vassiliev" <support@oledbdirect.com> wrote in message 
news:4243ecf7$1@newsgroups.borland.com...
> TADOTable with server-side cursor and TableDirect = true is very 
> effective for MS Access. This is only one configuration that allows 
> use of indexes and Seek().
>
> //------------------------------------------
> 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)
>
> "Arnie" <none> �������/�������� � �������� ���������: 
> news:42431ce8$1@newsgroups.borland.com...
>> "John Scott" <jscott@kw.igs.net> wrote in message 
>> news:4241e517$1@newsgroups.borland.com...
>>> My appliction uses ADO with and Access 2K database. I mostly use 
>>> tables and indexes - to order the data. I find that seeks and 
>>> other database actions are slow. Are there any parameters that I 
>>> can modify that might speed it up?
>>>
>>> John
>>
>> A little more info would be helpful.  If you're using TADOTable, 
>> don't. Use either the TADODataset or TADOQuery objects and use the 
>> SQL statement with a WHERE clause to filter your result and an 
>> ORDER BY to order it.
>>
>> - Arnie
>>
>
>