B
Burt
I'm working on a Windows app that pulls data from SQL Server, displays
it on various forms and grids, and allows the user to update, insert,
delete data. Some but not much business logic, just validation and and
some processing, like allowing the user to import data into the db
from upstream.
Trying to decide between datasets, and creating an object model
layer.
Articles like http://msdn.microsoft.com/msdnmag/issues/05/08/CuttingEdge/default.aspx
say datasets are best only for "prototyping", but another group at my
company is using them for a fairly complex app.
Does anyone have thoughts on this, or experiences to share?
Thanks,
Burt
it on various forms and grids, and allows the user to update, insert,
delete data. Some but not much business logic, just validation and and
some processing, like allowing the user to import data into the db
from upstream.
Trying to decide between datasets, and creating an object model
layer.
Articles like http://msdn.microsoft.com/msdnmag/issues/05/08/CuttingEdge/default.aspx
say datasets are best only for "prototyping", but another group at my
company is using them for a fairly complex app.
Does anyone have thoughts on this, or experiences to share?
Thanks,
Burt