Micha Nelissen escreveu:
On Mon, 10 Apr 2006 12:33:18 +0200
Joost van der Sluis <[EMAIL PROTECTED]> wrote:
If you don't want to limit, then set .Filtered := false; and use
FindFirst etc.
wich won't work with current sqldb, since filtering there simply adds a
'where' part to the query
On Mon, 10 Apr 2006 12:33:18 +0200
Joost van der Sluis <[EMAIL PROTECTED]> wrote:
> > If you don't want to limit, then set .Filtered := false; and use
> > FindFirst etc.
>
> wich won't work with current sqldb, since filtering there simply adds a
> 'where' part to the query.
> An which is much slo
On Mon, 10 Apr 2006, Joost van der Sluis wrote:
Not really. Sometimes I use a locate to find a record in a dataset. I
don't want to limit the records in that dataset with a filter.
If you don't want to limit, then set .Filtered := false; and use
FindFirst etc.
wich won't work with current
On 4/10/06, Joost van der Sluis <[EMAIL PROTECTED]> wrote:
> > > I'm busy implementing TBufDataset.Locate and friends. I had the idea to
> > > overload Locate like this:
> > >
> > > function Locate(const keyfields: string; const keyvalues: Variant;
> > > options: TLocateOptions; LocateNext : boole
> > I'm busy implementing TBufDataset.Locate and friends. I had the idea to
> > overload Locate like this:
> >
> > function Locate(const keyfields: string; const keyvalues: Variant;
> > options: TLocateOptions; LocateNext : boolean ) : boolean;
> >
> > So that it's possible to doe a 'locatenext'
>
> > Not really. Sometimes I use a locate to find a record in a dataset. I
> > don't want to limit the records in that dataset with a filter.
>
> If you don't want to limit, then set .Filtered := false; and use
> FindFirst etc.
wich won't work with current sqldb, since filtering there simply adds
On 4/7/06, Joost van der Sluis <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm busy implementing TBufDataset.Locate and friends. I had the idea to
> overload Locate like this:
>
> function Locate(const keyfields: string; const keyvalues: Variant;
> options: TLocateOptions; LocateNext : boolean ) : bo
On Sat, 08 Apr 2006 17:19:34 +0200
Marc Weustink <[EMAIL PROTECTED]> wrote:
> > I think .Filter in combination with .FindFirst/Prior/Next/Last is just as
> > powerful, so a LocateNext should not be needed.
>
> Not really. Sometimes I use a locate to find a record in a dataset. I
> don't want to
Micha Nelissen wrote:
On Fri, 07 Apr 2006 21:16:23 +0200
Joost van der Sluis <[EMAIL PROTECTED]> wrote:
function Locate(const keyfields: string; const keyvalues: Variant;
options: TLocateOptions; LocateNext : boolean ) : boolean;
So that it's possible to doe a 'locatenext'
But I saw that
On Fri, 7 Apr 2006, Micha Nelissen wrote:
> On Fri, 07 Apr 2006 21:16:23 +0200
> Joost van der Sluis <[EMAIL PROTECTED]> wrote:
>
> > function Locate(const keyfields: string; const keyvalues: Variant;
> > options: TLocateOptions; LocateNext : boolean ) : boolean;
> >
> > So that it's possib
On Fri, 07 Apr 2006 21:16:23 +0200
Joost van der Sluis <[EMAIL PROTECTED]> wrote:
> function Locate(const keyfields: string; const keyvalues: Variant;
> options: TLocateOptions; LocateNext : boolean ) : boolean;
>
> So that it's possible to doe a 'locatenext'
>
> But I saw that sqlite simply
Hi all,
I'm busy implementing TBufDataset.Locate and friends. I had the idea to
overload Locate like this:
function Locate(const keyfields: string; const keyvalues: Variant;
options: TLocateOptions; LocateNext : boolean ) : boolean;
So that it's possible to doe a 'locatenext'
But I saw that
12 matches
Mail list logo
