>>Of course, you'd have to check to see how the aViewParameters array was dimensioned first, so older apps wouldn't break with this change. It might also make sense to add a new property so you could select which view to requery when the REQUERY() method is called.
>>

Just another thought, if the property is set to zero, requery all the views. 1=view 1, 2=view 2, etc.

>Perhaps another way of looking at it is to use another business object for any views that requiring any type of processing. We sort of need a business object lite, especially one that does not include a cSessionEnvironment object! With this object which would automatically link into the parent/child tree, you can do a requeryallchildren from the parent.
>

I guess that makes sense. But, in my case even that seems like it adds unnecessary complexity. I just want to refresh my views ;-)

I'm wondering how you will tie these mini-bizobj's to your main object. Create a container that holds all of them? I know I sure wouldn't want to have to remember to drop my main bizobj onto a form, plus 10 other mini-bizobj's on top just to get things to work.