All,
We are converting a large vb6 application towards .Net2.0. Because of
the scale of the application we are doing an automatic conversion,
total code coverage upgrade. The problem we keep kicking into is the
updatebatch of a recordset.
This has a few "advantages" we don't see in .Net: (read disadvantage
for perfomance)
1. updateable inner joins (it can update every joined table)
2. It has metadata (primarykeys) in hidden fields ( like datareader
with commandbehavior.KeyInfo)
    If these fields are not given in the select statement.
    This will allow the updatebatch to reconstruct sql statements
everytime.
3 It will only update the changed values
Because of all the "flexibility" we are not able to use
storedprocedures.


So :
We will need the schemaInfo to get started.
Why did microsoft not override or made public the commandbehaviour on
the SQLDataAdapter?
(I don't want to use the datareader and then do a fill via that reader)


Later I want to use the commandbuilder, having solved the problem of
multiple table updates via joined queries. (Why did microsoft reject
this matter ?)

Is their an other way to simulate this behaviour?

Greetz,
Steven

TableAdapter Garbage
adapter.fill and progress bar
Close - No Dispose - Memory Leak?
Update problem with decimal value
DataTable and DataGridView