I'm assuming that the Account database table is a single table that is being
represented in 2 different DataSets. Am I correct? If so, why are you using
2 different DataSets for the same Database? A single DataSet can represent
an entire Database if desired.
It is important to note that simply creating a DataSet involves no database
interaction (other than the code creation process). Objects in the DataSet
are not populated until you say they are. In other words, there is no reason
that you should need 2 different DataSets that overlap, and in fact, this
could lead to problems with synchronization of the data across both
(disconnected) DataSets.
--
HTH,
Kevin Spencer
Microsoft MVP
Professional Numbskull
Hard work is a medication for which
there is no placebo.
"S Chapman" <s_*********@hotmail.co.uk> wrote in message
news:11**********************@u72g2000cwu.googlegr oups.com...
Is there any tool that generates Typed DataTables rather than Typed
Datasets? The trouble we are having is we have quite a few tables in
our database and a single table can be a part of more than one dataset.
If we use the XSD.Exe, the datatable definitions are repeated in every
dataset they appear in; causing our data definition layer to bloat.
Let us say there is a database table called Account which appears in
two dataset definitions - AccountData and TransactionData, XSD.Exe
creates two copies of Account datatable. This is very bad design as the
same underlying table is represented as different .net types.
We have looked at CodeSmith but it does not seem to provide any
out-of-the-box templates for what we are looking. We could write our
own templates but we are trying to avoid it to see if there is a better
way of coping with the problem.
Thanks.