A
Andrew
I'm a long time VB6/ADO and Java developer new to ADO.NET. I'm trying
to decide on best practices and I'd appreciate any assistance. I have
one specific question and another more general architectural one:
1. How can you pass around a disconnected DataSet/DataTable, make
changes to it and then pass it into a component for update? The
disconnected DataSet doesn't know it's UPDATE statement and the
DataAdapter is long since gone.
2. My previous n-tier designs encapsulated all data access into a
single component which knew how to load and store Business Objects.
The BOs didn't even have a reference to ADO. How are developers
handling this today? It seems a bit much to be passing around these
complex mini-databases (DataSets).
Thanks in advance.
to decide on best practices and I'd appreciate any assistance. I have
one specific question and another more general architectural one:
1. How can you pass around a disconnected DataSet/DataTable, make
changes to it and then pass it into a component for update? The
disconnected DataSet doesn't know it's UPDATE statement and the
DataAdapter is long since gone.
2. My previous n-tier designs encapsulated all data access into a
single component which knew how to load and store Business Objects.
The BOs didn't even have a reference to ADO. How are developers
handling this today? It seems a bit much to be passing around these
complex mini-databases (DataSets).
Thanks in advance.