>>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.