>I have a similar situation for a factory model: Orders, Parts as order line items and Processes (multiple processes per part). I handled it with parameterized views and page frames. Each page has a grid showing the view in a read-only grid, with text boxes to the side for editing. On the Orders page a you pick an Order and go to Order Detail. That page shows a grid of all parts in the order, and the third page shows all processes listed by part # (A summary page of all parts and processes).
>

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.

>Because there are often 1000+ parts to choose from for a given order I use a pop-up form with a grid that shows available parts and a checkbox for each record. You check the parts you want, and code adds them to the Line Item list. There's an incremental find textbox so you can move quickly through the grid.
>
>The same was done for Processes, but this is a much smaller list as a given part will have only 5-10 possible processes. I would have used a multiple choice listbox here, except I wanted to keep the user interface consistent.
>
>It's working very smoothly, and the customer is pleased with it. Her only change to the model above was that line items (parts) and processes (child and grandchild tables) be on the same page with a radio button to switch back and forth.
>
>Barbara
>
>
>>Barbara,
>>
>>First of all, thanks a lot for the reply. Yes, I want to allow user fill in Report configuration information, then add regions, say, South Boston, select towns (I'm thinking about mover's listboxes), North Shore (select another set of towns), etc.
>>
>> Table design looks like:
>>

>>  Config Table
>>       |
>>       Regions table
>>            |
>>            Towns per region

>>
>>Your suggestion about set deleted off and reusable CustomerID field makes sense. Today I modified tables structure to accomodate my second idea, but I haven't programmed anything yet, so I can revert back to CustomerID idea.
>>
>>Now I'm uncertain, how to actually design this form. What kind of interface should it be? Should I use views, and if yes, how?
>>
>>Thanks again, this gives me a start.