At 01:15 AM 03-01-01 +0100, you wrote:

>Your query works, thanks. But it doesn't solve my problem, even with explicit
>JOINs only the current row displays the correct data.

Guido,
See my previous message. You are seeing correct data only on the current
row because only one row (the current row) can be "valid" for the SQL
statement at a time. Jason could elucidate what's going on underneath, but
I suspect that IBO is fetching each time you scroll from row to row.

Obviously you must resolve this to meet your intentions, either by aliasing
the columns in 'B' and 'C' (if you want 18 columns) or by changing the
statement to a UNION of the three sets you are currently joining to the
base table, if it's six columns you want.

I can't guess from the current statement just what output you are wanting.

You might consider using TIB_Cursor and display the results of the current
fetch in a cursor grid, if reading is all you need to do...if you need to
perform DML based on the output, you would definitely need to read the grid
(using props and methods of TStringGrid) and push the values over to a
TIB_DSQL as parameters...

Can you clarify exactly what you are looking for as output to this query?

Helen

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________