>Hi Randy,
>
>I like to separate my views into a separate biz obj. It really gives you more flexibility, but I think the real question is which views will you be adding/deleting/modifying records in? Basically, I use this principal: If I am going to be updating the view, I use a separate biz obj, so that I can use all of the biz obj methods properly for the one view. For example: New(), Save(), Delete(), etc. If the two views are essentially lookups, you can load them with the one biz obj. In this case, it is a matter of whether or not your clientbizobj needs to use those views in order to stand alone. Another way to think about it, if you can instantiate your biz obj outside of the application, and navigate, add, save, update records, then your biz obj is rockin'.
>
>HTH

COOOOOL! Thanks Doug. I thought that was the case, but it sure helps to hear how other people are doing things.