Re: ADOTable.Locate Workaround?

From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 02/26/04 

Date: Wed, 25 Feb 2004 20:18:30 -0600

> I understand now that to use it I'd have to replace my table
>components with BetterAdoDataset components and recode for that.
There are a few different properties between these components but unless you are
creating TadoTables in code there should not be much code to do.

>But the fact is that if there's no way to get locate
>working I'm going to have to do that since without some type of find
>functionality the program's useless.
TadoCustomDataset.Locate has problems when there is a filter applied to the
dataset and in some cases where you use multiple fields in the locate.
You may not need to change all your TadoTable Components if they don't locate
under these circumstances.

>
> On the other hand I looked at adodb.pas and BetterAdoDataset.pas and I'm not
>sure that my skills are up to trying to take the CorrectlyLocateRecord function
>out of BetterAdoDataset and make it work in AdoDb, I mean if it were that easy
>wouldn't someone have already done it?
If you search the newsgroup Archives you will find other code to fix the locate
problem but it won't be any simpler to implement.

The easiest way for you to get just the locate capability of TbetterAdoDataset
would be to subclass the TadoTable then override the Locate method just like
TBetterAdoDataset does and use the same code for Locate and CorrectlyLocate.
Then you can just search and replace in your DFM files to replace TadoTable with
your new descendant component. 

--
Brian Bushay (TeamB)
Bbushay@NMPLS.com