A
Alan B
Okay so I'm using the Data Access application block in the Enterprise
Library. I'm using it to return a DataSet from an SQL Server (well, MSDE)
stored procedure. So that's an untyped DataSet. I have no access to the
DataAdapter used to retrieve the DataSet (the Enterprise Library classes
don't expose it AFAIK), so I can't create any TableMappings. I want to bind
the DataSet to Windows Forms controls, but I'm getting the old 'cannot
create child list' errors because there's no schema attached to the DataSet.
I can manually name tables and columns in the DataSet via the Tables
collection, and then bind. This is messy though, so:
1) Is that the only way to do it?
2) If I retrieve the DataSet, then use WriteXMLSchema, can I subsequently
use that saved schema against the returned DataSet?
3) This must be a very common thing that people need to do - why is is such
a pain in ADO.NET?
Library. I'm using it to return a DataSet from an SQL Server (well, MSDE)
stored procedure. So that's an untyped DataSet. I have no access to the
DataAdapter used to retrieve the DataSet (the Enterprise Library classes
don't expose it AFAIK), so I can't create any TableMappings. I want to bind
the DataSet to Windows Forms controls, but I'm getting the old 'cannot
create child list' errors because there's no schema attached to the DataSet.
I can manually name tables and columns in the DataSet via the Tables
collection, and then bind. This is messy though, so:
1) Is that the only way to do it?
2) If I retrieve the DataSet, then use WriteXMLSchema, can I subsequently
use that saved schema against the returned DataSet?
3) This must be a very common thing that people need to do - why is is such
a pain in ADO.NET?