>Jimmy,
>Fascinating :) How could you handle all these.
>"*THIS REPORT HAS FIELDS ACBUNDLE2, ACBUNDLE4, ACBUNDLE6, ACBUNDLE7......." ???
>Fields or memvar ? Reports work with tables, cursors. If at the same time there is a field named ie: ACBUNDLE2 in current workarea table.field takes precendence unless you precede it with "m.".
>As far as I understand each query is expected to return one element (or do you just use its first element). Also as I understand they absolutely return at least one element (otherwise type error with .. = bunlen12 ... ). This would mean you could combine the whole SQL into one.
>

select ;
> data1.bundle+data2.bundle...+data8.bundle as acBundle, data1.length ;
>from data1, data2.... ;
>where data1.grade + data1.siz = data2.grade + data2.siz ;
> and data2.grade + data2.siz = data3.grade + data3.siz ;
> and .... ;
> and data7.grade + data7.siz = data8.grade + data8.siz ;
> and data1.grade = gdValue and data1.siz = szValue ;
> order by 2 ;
> into cursor myCursor

grade + siz might need conversion depending on their type. Report would then be based on myCursor.
>Cetin


Close . . . very close. I apologize - the report has fields that reference MEMVAR ACBUNDLE2, ACBUNDLE4, ACBUNDLE6, ACBUNDLE7......."

In psuedocode . . .

data1.bundle(conditions:data1.grade=gdValue and data1.siz=szValue and data1.length=2)

is added to

data2.bundle(conditions:data2.grade=gdValue and data2.siz=szValue and data2.length=2)

is added to

data3.bundle(conditions:data3.grade=gdValue and data3.siz=szValue and data3.length=2)

is added to ...

saved as a variable to be referenced by the report

this is done EXACTLY