Mike

I believe I am almost there. What I have is similar to what Naomi suggested. A row with ID, parent ID and digit for sorting purpose that can be used color indication(maybe).
If the parent id and row id are the same then this is a parent row. The good thing I only have to deal with 1 level. If they asked for more than one level, it is time back for major design issue.

What the grid look like?
the left row will have minus sign (bold) for parent but blank for a child.
The child will have different color (grey). nothing like Christmas tree.

The child is read only if the parent is not selected. Did that in the When()

If I only could change the row color to dark grey if the parent row was not flagged and back to light grey when flagged, I would call it a day.

Mo

>>>Maybe the problem will become simpler if you rethink the approach. Why do you have a parent-child relation in the same grid? You might instead use two grids. Or a grid for the child table and separate controls such as textboxes for the parent record?
>>>
>>
>>In my old applications (such as Address Standardization, for example) we had different Status for each record (Auto-Corrected, Manually-Corrected, Failed, etc.) We used at the time grid with relations to display the Status as a description.
>
>Seems like that would be straightforward to do directly with a relation in effect and the parent table the main controlsource of the grid. Mo's objective seems more complex. Using a grid also seems problematic to me from a U.I. standpoint, if I understand correctly what he wants to do. It seems like other rows in the grid would be flashing like Christmas trees as you navigate through it. That would be a little too busy for me.