>Stephen:
>
>You can take control of the update process by creating your own DataAccess class for the business object by creating an update command that updates just one table. See "Creating Custom Data Access Classes" in the documentation.

Thanks, I guess that I can do that. I was doing it already.

>But I see a larger problem here. If you are doing a join to gather the data into one table then I assume in your DataTable you have columns for VendorID and VendorName. What if the user modifies the vendorid? You would have to manually update the VendorName to keep them in sync so you will need to retrieve a list of vendors from the database anyway. So your alternative is to not use a join. Keep separate tables in the DataSet and use a DataRelation to keep the VendorID Foreign key and vendor name in sync. Then you don't have to worry about creating the custom data access component.

Actually the interface they have a dropdown for Vendors and another for Types. They can add new Vendors or Types on the fly so that is not an issue I am worried about.

I'll look into the realtionship inside of the dataset later today.

Thanks.

>Either way should work.
>
>>I have data for the datagrid that really needs to show the lookup columns. Yet when I write the dataset back, it errors on it's multi-table aspect.
>>
>>It's an inventory piece with an InventroyType, as well as a Vendor column.
>>
>>I can display the data with the 3 table join, I just can't save a new record.