Hi Francisco

I think you may be a bit confused as to business objects and usage. For what you are describing, I think you are confusing a business object with a data services tier. A business object ensures that the business rules for the organization are followed -- although it probably does include some data writing, while a data services tier (one or more objects) might be spawned to manage the actual read/write/delete for raw data.


>Hello, i have 2 tables, 1 table have the properties from a object, and second table have the information for working with users, like invoice_properties and invoice , i need create a business object for every table?, a business object for invoice_properties and another business object for invoice?, or i can put the 2 tables in one business object?, the invoice_properties only have the behavior and invoice all the data, but the table invoice save the data in way how is setting the invoice_properties, some one help me?, i try to make a 1 view for 2 tables but this is a problematic way for update information, then i need use 2 views, then i need 2 business objects too?.
>
>I have that doubt so that a business object must abstract the properties, data and methods, and think using 2 business object for the same entity is not a good approach.
>
>what you think?
>
>Thanks
>
>Francisco Morosini