>Hi all,
>
>May be the wrong place this but since I am working working with MM I thought I'd ask opinions.
>
>1. Parts have components. Components have ratings. Ratings are grouped under categories (Descriptions) -- there may be multiple categories with the same components assigned to the same part.
>
>
>2. Categories is Primary View.
>
> Ratings are a child to the category -- changing category changes the ratings displayed and which part it belongs -- Table buffered
>
>
>3. A new Category is created -- This is where the problem lies.
>
> On a new category the display should be the components for the selected part. So if the Part has five components the display should be those five plus a rating of zero. In a Parent-child relationship using MM I can have the framework create me a new child record when a new parent iis created but I need X number of child records.
>
> My thinking so far is to create a standard parent-child view for editing. When adding, I was thinking if having a view that gets the components for the selected part then manually appending the records into the child view with a loop. That way I can maintain the Parent-Child relationship code
>
>Opinions anyone? Right track? Wrong track? Better way to do this?
>
>Thanks
>
>Bob


Why not use an event to build the logic between both business objects?