>>>>>In vfp60 when you SET RELATION between parent and child...
>>>>>What happens if your child table contains a record that your parent
>>>>>table does not have..how to you catch that?
>>>>
>>>>If the relation is parent to child. Then when you position the parent the children will show up. If you have an orphan than the only way to find it is set the relation child to parent and move the child record. When parent is EOF then I do something such as delete the child or generate a report etc..
>>>>
>>>>HTH
>>>Hi Bret and thanks for the information... :)
>>
>>Robert,
>>
>>The referential integrity features of VFP will help to prevent this type of situation - like not being able to delete a parent record while child records are present, but of course you have to start with a "clean" file first if you're adding the rules after some data already exists.
>Cindy, I am dealing with two tables given to me by management. I have to deal
>with these tables the way they exist...thanks

Well, now you see the value of built-in referential integrity! ;-)

If you used SQL with a FULL JOIN for your report you could check for NULLs in the parent part of the record.