>>>Look at outer-joined cursor. Does it really contains #215 record?
>>
>>Starting a new thread. I hate it when the thread gets too far
>>to the right of the screen.
>>
>>Yes here's the code.
>>
>>SELECT &lcALLFIELDS FROM GLS!LM10, GLS!LM10TRS WHERE ;
>> lm10.CDLRNMBR = lm10trs.CDLRNMBR ;
>> INTO CURSOR LM10VUE ;
>> UNION ;
>> SELECT &lcNOTRSFIELDS FROM GLS!LM10 ;
>> WHERE lm10.CDLRNMBR NOT IN ;
>> ( SELECT lm10trs.CDLRNMBR FROM lm10trs )
>>
>>
>>Dan
>
>I cannot believe that this UNION will work, it cannot be &lcFiELDS in both Selects. Do you select any fields from lm10trs?

I know, I know, I saw the help and it replaced the other fields
with 0 when only selecting from one database within the UNION.
But it does work. I'll double check my code and make sure that
I'm not using any set fields or anything like that.

. . . . . . . . .

Ok. Just checked. You're right when the data from the trs
fields of the empty records has incorrect data. I altered
the select statement ( check above ) and that fixed the the
incorrect data but not the report header problem.

Dan