>All,
>
>We have a .Net contractor that uses business object to encapsulate actor information. He says that the business object should have properties for only the table fields that are to be displayed, but I have always used business objects with all table fields represented as properties. He says that he does this to conserve memory, but my understanding of business objects is that the objects controls and encapsulates all information regarding the associated actor.
>
>Is there a concensus regarding business objects?
>

That doesn't sound right to me. How can you make a general design decision about what will be displayed? What might not be needed to be displayed today, will probably be needed tomorrow. The business object is supposed to be independent of the UI, so why bind it's design to a UI?

Besides, if you're using .NET anyway, memory usage of some extra properties in your objects is pretty far down on the list of things to worry about. The framework is pretty beefy ;-)