The Session class was designed specifically to handle business and data objects and middle tier DLLs.

>Thank you all for your suggestions. Too bad the three of you suggest three different approaches and I don't want to offend any one of you <g>.
>
>Seriously though. Creating composite object at design time is not a priority for me (honestly I don't even understand the purpose of the composite object). Therefore container does not seem to be the right fit for my needs. And I don't mind putting extra time/work to pass data across session boundary. But to work with session class is PITA because you have to do it all in .PRG.
>Custom class is nice but lacking the DataSession property to isolate the data. I don't have VFP 9 yet, just ordered it yesterday, but I was hoping that by now (ver 9) VFPT would have a class that have benefits of all three suggested, specifically designed for business classes.
>