Hi Sam,

>I have an SQL table that has close to 100 columns. Some users need to reference all columns, but other users need to only reference a few columns in that table.
>
>Is it normal practice in MM .NET v2.4 to create multiple business objects and business entities and stored procedures for the same table so that only the columns needed by each user are referenced, or is it better to only use one set of objects that use all columns but only display the columns needed in the user interface?
>
>It looks like either approach will work, but dealing with 100 columns when only a few columns are needed seems like a waste of resources, but creating and keeping track of multiple business objects, business entities, and stored procedures is no piece of cake either.
>
>Suggestions?
>
Just my thoughts. How many rows would you typically be retrieving in either case? If the data is lots of rows with lots of columns, then I would probably consider making seperate business objects. If there is only two cases you are talking about, then it wouldn't be that difficult to instanitate the business object based on the user case.

Cheers
Tim