Actually its not that hard. Just create an array property in your base list control, and in its requery method, fill your list. Having that extra layer of abstraction allows you to manipulate the list without affecting the underliying table or moving its record pointer. You wouldn't have to change any indexes because your decoupled from the underlying table so your relations will stay in tact.

The reason I'm saying this is because I have an app that uses complex 3 level relations and it also allows you to edit the child tables. I got everything to work, but needed workarounds. Just for kicks, I thought about decoupling the grids. When all was done, I was very happy with the results and swore I would never go back to direct coupling except for the simpliest situations.

Charlie