>Hi,
>
>So far I have been creating one BIZ object for one table. But I am wondering if there is a better design for cases of parent/child tables and ancillary tables. For example, P.O. Header table and P.O. Item table. One approach I am considering is to instantiate P.O. items BIZ object in the INIT of the P.O. Header BIZ object. And then "deal" with any updates for P.O. Items within P.O. Header BiZ object. How do you design your BIZ objects for the cases of parent/child tables?
>
>TIA.

Please go check out my blog post on building Parent-Child aggregate models in FoxPro. I've built this exact parent-child structure on top of the West Wind wwBusiness classes. I even have a sample app I share with folks who want to play with it.

http://mattslay.com/west-wind-client-tools-for-vfp/


.