>BOb,
>
>>My question is, can't this be a bit more encapsulated. For example, in the afterrowchange of the grid, instead of using this.oBizObj.getalias(), can't you do a thisform.oBizObj.getalias() ???>
>
>That would work well only if the form's primary business object is truly the object you want to associate with the grid. If you have multiple grids on a single page (as I did in a form I created last night!) you'd end up with a serious contention problem if the Framework assumed the primary business object.
>
>This approach offers the most flexibility because you can assign any business object...whether primary or not...to the grid.
>
>Regards,

Then maybe I am missing it. How do you assign a business object to the grid? You have to do it in the form init programatically?

What I am saying is, ins't there a way where the grid could have a property that holds the name of the bizobj which it represents?

BOb