<i><font color="#663300">Hi all
1. I have an bo_maccounts. This is used in the data entry for mAccounts and I have methods in this BO for generating lookup cursors based on the mAccounts table for use in the same data entry screen. Is it okay?
2. A few reports like Accounts Listing, Trial Balance will be based on the table mAccounts of which the above BO is derived. Should I make the bo_maccounts a do all or should I have a different BO for these reports?
3. Also Trial Balance is using other tables for generating current values, what should be the method with CB in mind.
Thanks all for responding to my previous queries. But the list seems to be silent these-a-days.
</font></i>
You couldn't be more right! This 'community' appears to be non-existent.
Anyway, my 2 cents is that I have subclassed BO's appropriate to the data that I am working with... child or parent (separate bo's) if the table is both a child and a parent I find that using more BO's makes my development life easier rather than trying to make fewer BO's do everything! I'm also extensively starting to use views where the relationship is already defined and the lowest child is the only updatable table... that is making my life easier too!
HTH
another lonely Codebook user -- struggling through
Lynette
Lynette
ltillner AT yahoo .D.OT com
©2002 Lynette Tillner |
