>>
>That's the one (big) thing I don't like about using a DataSource with a winform. It is breathtaking how much ADO code gets generated for you, except the UI is bound pretty directly to data. That's an abomination in any N-tier architecture I have seen.>>
>>I'm not sure what you're referring to by "datasource". If you're talking about tying the actual database to the UI, then yeah, that's bad! But DataSets are fine. They aren't tied to a database (unless you use TableAdapters in your DataSet WHICH SHOULDN'T BE DONE ... IMHO anyway <g>)
>>
>
>Data menu / Add New Data Source
>
>I understand that the DataSet is not the same thing as the back end database, but if you use the wizard they are in fact mapped 1:1.
I would take a look at the MVP Pattern.
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
