>Hi Erik!
>
>But what is the Business object exactly? Never saw the Codebook, so I don't
>know about this creature ;). (Hope that I will found this book with CD in
>Germany) Can anybody here tell me (even in private email) more details
>about this>
>
>>I believe that the business class concept (ala codebook) encompasses the
>>functionality that you are looking for. Rather that placing the code that
>
>>handles data for an entity (usually one table) in a form, place it in a
>>non-visual class that can be placed on any form, or called from another
>>procedure.
A business rules object is simply three-teir architecture. In my opinion, CodeBook adds lots of unneeded complexitey. Not because of adding a business object, but just the way they implement all their classes.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer