> 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.


Actually, it will work very easily. In fact less work than you imagine. The bizobj's, in their init, register themselves with the form. One of them is marked as the primary object (usually the parent). A requery of the parent automatically (there is an lrequeryallchildren property) will requery all of the child bizobjs. So if you have 10 views with parameters, each of their requery methods will fire.

I have just been messing with changing the business object from a container (with a session object and dataloader object) to a label object. I have got it working just the same. I have to add a session object to the form, but not a big deal. I also modified the sessionenvironment object to check the goapp.oenvironment.osession object properties for global settings. This works very well too. Global settings that are global!

For instance, the client form in the sample project manager app loads 3 sessionenvironments and goes through all the set statements (more than 20 I think) all three times. Hardly necessary!