Another thing that could mess it up is if somewhere in your form you select the auth table, and leave it selected, maybe when you open your tables, you mentioned you do it in code right?, after you open your tables just select person, and whenever you handle auth in some way, select person afterwards.

If you still have problems then rebuild the form ( a new one ) piece by piece starting with only the related tables and the grid, until you find out what's wrong, this method has worked for me every time, good luck.

>Did that:
>

>use person order main in 0
>use auth order main in 0
>set relation to id into auth
>brow
>sele auth
>brow

>
>and click on person browse screen and move the record pointer, the auth follows it's relationship, as expected. FWIW, I have the character field ID indexed tag as UPPER(id), even if it's all numbers, but it helps me to remember that "everything" in the CDX is UPPER(blah). I even tried RelationExpr: UPPER(id), does not make any difference.
>
>I checked the project again this morning (in hopeing that giving the VFP a overnight rest with PC off), same thing. Doesn't matter, but it's VFP 6.0 SP5.
>
>Chuck
>
>>Check your index I see you have main for child order and ID as relational expression, unless main's index expression is something like ID + Something else, your relation will not work.
>>
>>Also you could try it out without a form, open your tables from the command window or the data session window, set up the relation and browse them both at the same time, move through PERSON and AUTH should cnage accordingly, if not, then your index expresion is at fault.
>
>>>>>VFP 6.0
>>>

>>>>>Grid: Grid1
>>>>>ChildOrder: main
>>>>>LinkMaster: person
>>>>>ReadOnly: .T. - True
>>>>>RecordSource: auth
>>>>>RecordSourceType: 1 - Alias
>>>>>RelationExpr: id