>>>Robert,
>>>

>>>SELECT Table1.*, Table2.* ;
>>>    FROM Table1 FULL JOIN Table2 ON Table1.SomeKey = Table2.SomeKey ;
>>>    ORDER BY SomeField

>>>
>>>
>>>
>>>>>If you used SQL with a FULL JOIN for your report you could check for NULLs in the parent part of the record.
>>>>Hi Cindy and yes I see the value of built-in referential integrity.
>>>>Could you send me a small sample of code of how to use SQL with a FULL JOIN.
>>Thanks Cindy - Is this the same as a SET RELATION, but using a SELECT statement?
>
>No. Set relation will leave out orphan child records.
>
>The purpose of the FULL JOIN is to show NULL in the "parent" fields for an orphan child record, NULL in the "child" fields for a parent without children, and all fields filled in for parents with children.
>
>Also, set relation is done on the actual tables, the result of an SQL SELECT statement will result in a "copy" of the data - fine for a report but maybe not for data editing.
ok - great Cindy and thanks... :)