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.

Barbara


>Barbara,
>
>Did you have 3 p-views? One per table? I was thinking about using pageframe too, but not sure, it's applicable to my situation. The user should fill only one record in the parent table (he/she selects CusomerID at early stage, so I want to give them either blank record with CustomerID pre-set or record to modify). If it's an empty record, they should first fill in info in parent table, then create Regions (say, I will have button Add New Region, which will bring me to another page). After they fill in Region Name, they should choose towns for this region (using mover's listbox). Ok, sounds doable now.
>