Your statment " i use the join the create e new tables" is misleading. If you
are using a JOIN clause, you are getting back one Datatable. Therefore, your
update, assuming you are passing this table into a DataAdapter, must have SQL
that is smart enough to know which columns belong to which of the original
joined tables and take care of updating each table.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
MetaFinder: http://www.blogmetafinder.com 

Baddy,

A Select with joined tables creates one resultset which is by you gotten as
I have read  ir right using the Fill from the SqlDataAdapter.

There is no information from where the table comes, where the fields are
from, how much it is compressed etc etc.

The only possibility you have is to create your own Insert, Update and
Delete SQL scripts (sprocs or just as inline text in your DBlayer) and then
process those with seperate ADONet SqlClient.SQLExecuteNonQuery Commands.

Be aware that you have to do then yourself all concurency checking,
relational checing and act row by row what to do. In my idea a hell of a
job. I don't think that this is ever really done in a production
environment. For sure I have never seen samples about that in .Net
newsgroups.

For this kind of jobs are seperated Related DataTables used inside a DataSet
or whatever. (Aroud those are tools to create the needed Update, Delete, and
Insert scripts.). If it is about one none related sinlge datatable (not
joined) with less than 100 fields you can use as well then the
SqlClient.SqlCommandbuilder.

This is for versions before 2008, however I am me not aware that there has
changed anything about this in version 2008.

Cor