>>So just for internal reference (and an internal bet), did you do this? In Fox, that is. I'm not expecting that anyone did it in .net, that's where "things are done in a different way", as I was told.
>>
>>(on the question of how to do it in c#... I don't care, let him suffer, and I don't want to know)
>
>In our ASP.NET MVC/C#/EF application we have such functionality implemented. There is a possibility to open the new form for editing the "lookup" table and then refresh data back. I forgot right now the term we used for such functionality and it was implemented by one of the contractors working on this project (he is no longer working). In any case, we do have such functionality but it opens a separate page in a new browser window (not in the same page).

New page in web or a new form in desktop is just the shape of it, but internally the logic should be the same. Though in a web app you usually don't have stale data in local cursors, being stateless means you requery everything every time, just take care not to have too much of it, so the problem of how to requery one cursor (or equivalent) is not so prominent.

(Siriusware? My best to folks there)