Subject | Problem with Locate and Join |
---|---|
Author | scr0546 |
Post date | 2006-05-09T08:58:44Z |
Hi
I have a strange problem with TIBOQuery (v 4.6A), when I want to
locate a record
1) Select A.NR, A.StartDate, A.ForeignID ...
From Table1 A
Order by A.StartDate desc, A.NR
Locate('NR',123,[]) returns true, thats OK.
2) Select A.NR, A.StartDate, A.ForeignID ...
From Table1 A
LEFT JOIN Table2 B ON B.NR = A.ForeignID
Order by A.StartDate desc, A.NR
(A.NR and B.NR are the primary keys in each table)
Locate('NR',123,[]) returns false,
but the record Nr = 123 is still there.
When I set the filter "A.NR=123" before calling locate,
then the (single) record in the dataset is found:
Locate('NR',123,[]) returns true.
note: it's independent from adding B.x ... fieldnames to the
select-statement or not
thanks for help
joe
I have a strange problem with TIBOQuery (v 4.6A), when I want to
locate a record
1) Select A.NR, A.StartDate, A.ForeignID ...
From Table1 A
Order by A.StartDate desc, A.NR
Locate('NR',123,[]) returns true, thats OK.
2) Select A.NR, A.StartDate, A.ForeignID ...
From Table1 A
LEFT JOIN Table2 B ON B.NR = A.ForeignID
Order by A.StartDate desc, A.NR
(A.NR and B.NR are the primary keys in each table)
Locate('NR',123,[]) returns false,
but the record Nr = 123 is still there.
When I set the filter "A.NR=123" before calling locate,
then the (single) record in the dataset is found:
Locate('NR',123,[]) returns true.
note: it's independent from adding B.x ... fieldnames to the
select-statement or not
thanks for help
joe