Hi Jason,

It sure did help. It's working well. I set up the OrderingLinks already like this : MYCOL=ITEM=1, but I didn't know you could add the POS attribute. Thanks a lot again for your advice !!

Greetings,

Nico Callewaert
Trislot n.v. - Waregem - Belgium
ncw@...
nico.callewaert@...

----- Original Message -----
From: Jason Wharton
To: IBObjects@yahoogroups.com
Sent: Saturday, May 19, 2001 9:03 AM
Subject: Re: [IBO] Query / join question


I have a table that is about 8,000 records as a lookup table. I use the POS
attribute on the OrderingLinks property. This makes it so that the query
will only fetch in a section of the records necessary instead of the whole
dataset.

It makes it behave a little like it was a detail of a master detail
relationship.

Give it a shot and let us know.

I recommend that you use POS=0.

Thus, your OrderingLinks entry will look something like this:

MYCOL=ITEM=1;POS=0

This is assuming it used to look like this:

MYCOL=1

Hope this helps,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com


----- Original Message -----
From: "Nico Callewaert" <nico.callewaert@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, May 18, 2001 11:31 PM
Subject: [IBO] Query / join question


> Hi,
>
> Could a IBO master give me some hints with this pleaseeeee ?
>
> Thank you, Nico
>
> ----- Original Message -----
> From: Nico Callewaert <nico.callewaert@...>
> To: <IBObjects@yahoogroups.com>
> Sent: Friday, May 18, 2001 8:57 PM
> Subject: [IBO] Query / join question
>
>
> > Hi,
> >
> > I have a little problem. I have a query like this :
> >
> > SELECT A.OrderNo,
> > A.CustNo,
> > A.... etc, etc,
> > B.Name
> > FROM Order_Comm A
> > JOIN Cust B ON B.CustNo = A.CustNo
> > WHERE A.OrderNo = :qOrderNo
> >
> > Keyrelation set to Order_Comm
> >
> > Everything ok, but the users of my application were complaining, when
they
> insert a new order, after they entered the customer number, they expect to
> see immediatly the name of the customer. Of course the name only appears
> after they save the record. After that I decided to remove the JOIN and
> use a seperate query to retrieve the customers name, by setting KeyLinks
and
> KeySource. They get what they asked, but the problem is the customers
> table is getting bigger and bigger, now I already have approximatly 3000
> records. With KeyLinks doesn't seem the best solution. A table with
3000
> records cannot be called "lookup table" anymore. How could I solve this
> the best ?? All I know some users could be tough.
> >
> > Many thanks in advance,
> >
> > Nico Callewaert
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
> >
> >
> >
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/




Stamp powered by www.mailround.com

Click here to join YOPTIN and WIN COOL PRIZES




[Non-text portions of this message have been removed]