>>Nadya,
>>Yes, 3 p-views, each one based on the PK of the parent table. I needed the pageframe because of the amount of information they wanted displayed on a 600 X 800 screen (these are running in a factory, and the monitors are small).
>>
>>In your case you might get by with a a single screen if there weren't too much information being displayed for the parent and region levels. Movers, since they are usually lists, won't work smoothly if there are 100+ items, simply because LISTS don't work well. They also take up more space than a popup form does, which was important in my app. But in your case it sounds feasible to use movers.
>
>You might be right, I'm not sure about movers... I have Cetin's multiselect listbox as alternative. I'll think about it.
>

FoxyClasses moverlistx support SQL and fast. Additem approach if could ever worked would be sloooow with long lists.
MoverListXL even much faster supporting other features of multiselectgrid.
However you could just use the Multiselectgrid too as you mentioned.
Cetin