I don't personally use Codebook, but have begun to implement the business object concept in my framework nonetheless. Perhaps someone more familiar with codebook would be able to explain better. Basically a business object is a custom class that handles the data functions for an entity that is represented in your database (customer, supplier, transaction, etc) the class would handle any universal rules that apply to the records and contain the code to rectify any discrepancies. For instance, on a customer form, to add a customer:

cmdadd.click:
thisform.customer.save

instead of:
thisform.save

or

tableupdate()
... or whatever...

It enforces using the same rules for records in that table (or group of tables) wherever that table is used. All forms are then required to access the tables through the business object instead of directly. Whenever another form needs to modify data in a certain table, drop the business object on the form and call its methods.

>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.