>This is my first middle-tier project, so I can't say that what I am doing is a best practice. What I do is have a 1-1 correlation between my SQL Server tables and my business objects. Each business object, ex. Customer, focuses only on dealing with its corresponding table.
>
>Sa far, these are pretty light-weight: I insert a new record, update an existing, load a record, etc. Also, I may retrieve the customer's credit limit within the object, return their most recent Order #, etc.
>
>When objects need to interact with each other, as when a customer places an order, I use an event object. The event object handles the interaction between the various business objects. So far, this is where the complex business logic is going, in my event objects. Each object itself does not do very much, but when theyu interact, as when a customer places an order, things get more complex.
>
Chris,

Your strategy is a generally accepted method. Another method would be to compile your bizobj's into dll's and have com+ handle event management.