Here is how I see your situation:

You need something that provides you with a dynamic set of views that are handled by one biz obj. Is this correct?

What you can do, is create the views that the biz obj will load on the fly. I am actually doing something similar.

For example: The biz obj of interest would not have any views (ov_whatever) in its data environment class. It would actually create and load the appropriate views in the PostInitHook() of the data environment class. I have a similar situation, where I am dynamically creating views (because our app allows the user to create user-defined tables), then I have a biz obj that loads the views dynamically.

>SIG new: Yes if there are three reccords we need three controls. Wilma and Betty are related only that they are in the same table and are displayed on the same form. Another example...
>
>The problem here stems from an unusual interface where multiple edits are viewed and used silmutaniously, like you would in a grid, but they are definately not in a grid. So imagine having to do a grid without a grid or browse window in the MM framework.
>
>As Doug Suggests the simple answer is to have two buisness objects with different views. The problem is that we dont know how many objects we will need ahead of time, its up to the user. (doug: its multiple procedures in a procedure report) The format is the same though. So we make a view for the buisness object that has the fields we want to edit. Now if I instatiate that view on the same form more than once, the framework will not open the view for the second buisness object. It sees a view of the same name already open in the forms data session and it dosn't open its own view. Further there is no way provided to assign a view a custom alias.
>
>REX:
>SFJI, but if you have three records, do you need three controls? What is the relation between Wilma & Betty?
>
>
>SIG original:
>Ive got two reccords in a table of customers. The first is for Wilma and the second is for Betty. Ive got a form with two customer controlls on it. Both need to be bound to views of the customers table. The first needs to be bound to the reccord for Wilma and the other for Betty, at the same time. Both are displayed on the screen and editable, indeed they are based on the same class. But if I bind them to the same view they will show the same reccord, thats what I don't want.