Ed Leafe wrote: > > >>In your example, it sounds like you would have an Account bizobj as your PrimaryBizobj. There would be >>a child Address bizobj to handle the address table, with a 1:M relationship. That bizobj would have a >>child bizobj for phones, etc. >> >> That's what I meant by one bizobj per table. You can have as many >> bizobjs as you like on a given >>form. >> >> Business objects (bizobjs) are essentially query results, but with added logic for enforcing business >>rules for the data. You bind your controls to bizobjs, so in that sense, it's like Access, but you have a >>lot more control over how your data is handled. >> >>-- Ed Leafe > > Thanks, that's a relief. Is there any documentation on this, or maybe an > example I can look at the code on? > > > > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users > Searchable Archives: http://leafe.com/archives/search/dabo-users > This message: > http://leafe.com/archives/byMID/[email protected] > >
-- View this message in context: http://old.nabble.com/Need-direction-for-project-tp29378019p29392596.html Sent from the dabo-users mailing list archive at Nabble.com. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
