Hi Matt,

>Wow!!! That never ocurred to me. That is cool... I've gotta make sure Tim reads this.
>
>So, what you recommend between this method vs. having a JobItems BO and Parts BO with a Releationship to pull the PartDescription into the grid?
>
>

I amn following this thread for sure. I should have mentioned that option but didn't think about it. I would suppose there are times to do it either way depending on the situation. Relating the Biz Objs would give you the benefit of updating. If you look at the way the jump start is done, the Shipper field that is in the order is put on the form with a combobox allowing the user to change the shipper on the order. It displays the shipper name but updates the order with the shipper_Id. you wouldn't do this as easily with the view or proc method. However for just a list or report of somekind, it might make sense to do it with a view.
Take care
Tim

>
>
>
>>Matt,
>>
>>>So, I need to understand how the JobItem Entity would handle the PartDescription column since it is not present in the Entity model that was generated from the Business Layer Generator. Since that field (the PartDescription) is not in the JobItems table, I was not able to pick it when generating the JobItems BO and Entity.
>>
>>You can generate entity objects from stored procedures (and views) in addition to tables. You can regen the entity from the stored procedure and it will include the PartDescription property
>>
>>Best Regards,