Re: Paradox's FindNearest is faster than ADO MsAccess's Locate!!

From: Troy Wolbrink (troy.wolbrink_at_ccci.org)
Date: 01/02/04 

Date: Thu, 1 Jan 2004 23:29:31 -0500

1. Use the Jet provider.
2. Set the index to match fields you are doing the locate on.
3. Use the .Seek method instead of Locate.

Consider using TTntADODataSetLX. It will help you in two ways. It will
support doing a locate on Unicode values. And it will automatically
redirect any calls from Locate() to Seek() when the index is set. Keep in
mind you'll need TableDirect and ServerSide cursors using the Jet provider.

--Troy
http://home.ccci.org/wolbrink/tnt/lx_controls.htm

"Fatih Tolga Ata" <fatihtolgaata@yahoo.com> wrote in message
news:3ff33851$1@newsgroups.borland.com...
> hi,
> MsAccess support unicode chars, but paradox doesn't. However Paradox is
> faster than ms access. I use access with this properties:
> TableDirect:= True;
> CursorLocation := clUseServer;
> CursorType := ctKeyset;
> Provider is "M$ OLE DB Provider for ODBC Drivers"
> Also I use index. With this properties, ms Access's Locate function is
about
> 4-5 sec. But paradox's FindNearest or Locate function is about 0,5 - 1
sec.
> What can I do for improving Ms Access's performance like paradox.
>
> sorry for my poor english.
> Regards,
>
>