>>So I believe your saying that if I want to manipulate child data for a particular parent I have to use a View/Cursor.
>>
>>It doesn't look so complicated with your example.
>>
>You do not have to do it that way. You can accomplish the same thing with a relation set into the child table and setting the child order descending. Many of us use updatable, parameterized views.

Well, the parameterized view would allow me to manipulate "any" record not just the first or last, correct?