Bonnie

I started out with untyped datatables and progressed to strongly typed datasets. Many obvious benefits there.
Is there such a thing as a strongly typed datatable that's not part of a dataset?
If so, what benefits do ST datasets provide that ST datatables don't?





>By the way, there's some movement to not use DataSets but DataTables, or even better Entity Framework. Just something else to throw onto your learning list.

Really? Why in the world would one want to use only DataTables? There's really little overhead in having a DataSet, even if contains only one DataTable. And then you can easily add additional DataTables when/if you need them. Be consistent and always use a DataSet for transporting your data around between objects and layers, instead of sometimes using a DataSet and sometimes using a DataTable.

Unless, of course, you meant individual methods that only work on one DataTable, then yes, passing only the DataTable into the method would be ok. Or with DataBinding.

As far as Entity Framework, I still have not taken a taste of the Kool-Aid on that one, so I can't comment. <g>