Thanks, I'll check it out.

>Frank,
>
>When I need multiple Business Objects to perform something, I create a Business Process Object. Check it out in the Dev Guide. It sounds like what you mention below as a BOManager.
>
>HTH
>
>>>>Perfectly OK in my opinion. I guess it should be since I do it. :-)
>>>
>>>I think what is/was bugging me is that in my VFP framework I would have done this at a level higher than the BO. I use a BOManager that coordinates all the separate BOs and calls the various bits in order to do the calculation.
>>
>>BOManager doesn't sound like the sort of class where you would want to implement specific code such as that. However if you had several functions that needed to collaborate with different business objects, you could create a class in your business object project that would be the intermediary. The thing to probably watch out for though is keeping from just adding a bunch of un-related stuff in there. You could have a class for instance called PolicyManager that you used to hold methods that would instantiate different business objects to do policy specific work. Nothing wrong with that approach and I have done similar things.
>>Tim